CVE-2016-8900

CRITICALNVD 9.89.8—Trending — 3 sources updated this week

9.8

Exponent CMS version 2.3.9 suffers from a Object Injection vulnerability in framework/modules/core/controllers/expTagController.php related to change_tags.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 66.8%
KEV: Not listed

Published

May 24, 2019

Last Modified

November 21, 2024

References (4)

cve@mitrehttp://www.openwall.com/lists/oss-security/2016/09/30/5
cve@mitrehttps://github.com/exponentcms/exponent-cms/commit/fdafb5ec97838e4edbd685f587f28d3174ebb3db
af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2016/09/30/5
af854a3a-2127-422b-91ae-364da2661108https://github.com/exponentcms/exponent-cms/commit/fdafb5ec97838e4edbd685f587f28d3174ebb3db

Weakness Classification(1)

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

CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection)

Data Freshness Timeline

(refreshed 11× in last 7d / 18× 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-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 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-27 19:09 UTCEG score recompute
2026-05-27 19:09 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-24 16:44 UTCepss_batch
2026-05-23 18:05 UTCOSV refresh

Frequently asked(5)

What is CVE-2016-8900?

CVE-2016-8900 is a critical vulnerability published on May 24, 2019. Exponent CMS version 2.3.9 suffers from a Object Injection vulnerability in framework/modules/core/controllers/expTagController.php related to change_tags.

When was CVE-2016-8900 disclosed?

CVE-2016-8900 was first published in the National Vulnerability Database on May 24, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2016-8900 actively exploited?

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

What is the CVSS score of CVE-2016-8900?

CVE-2016-8900 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2016-8900?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-8900, 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-2016-8900

Explore →

Is Your Infrastructure Affected by CVE-2016-8900?

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

Start Free Scan →Browse All CVEs

CVE-2016-8900

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2016-8900?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)