CVE-2015-1631

NONECVSS 0.0Trending — 3 sources updated this week

0.0

Microsoft Exchange Server 2013 SP1 and Cumulative Update 7 allows remote attackers to spoof meeting organizers via unspecified vectors, aka "Exchange Forged Meeting Request Spoofing Vulnerability."

CVSS v3: —
EG Score: 0.0(none)
EPSS: 92.6%
KEV: Not listed

Published

March 11, 2015

Last Modified

May 6, 2026

References (4)

secure@microsofthttp://www.securitytracker.com/id/1031900
secure@microsofthttps://docs.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-026
af854a3a-2127-422b-91ae-364da2661108http://www.securitytracker.com/id/1031900
af854a3a-2127-422b-91ae-364da2661108https://docs.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-026

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-284Improper Access Control

Data Freshness Timeline

(refreshed 13× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:10 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:11 UTCEG score recompute
2026-05-28 13:11 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-24 16:43 UTCepss_batch

Frequently asked(4)

What is CVE-2015-1631?

CVE-2015-1631 is a none vulnerability published on March 11, 2015. Microsoft Exchange Server 2013 SP1 and Cumulative Update 7 allows remote attackers to spoof meeting organizers via unspecified vectors, aka "Exchange Forged Meeting Request Spoofing Vulnerability."

When was CVE-2015-1631 disclosed?

CVE-2015-1631 was first published in the National Vulnerability Database on March 11, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2015-1631 actively exploited?

CVE-2015-1631 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 92.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2015-1631?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-1631, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-1631

Explore →

Is Your Infrastructure Affected by CVE-2015-1631?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2015-1631

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2015-1631?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(4)

Related CVEs(same CWE)