Extbase in TYPO3 4.3.0 before 6.2.24, 7.x before 7.6.8, and 8.1.1 allows remote attackers to obtain sensitive information or possibly execute arbitrary code via a crafted Extbase action.
CVE-2016-5091
HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 2.4%, top 15% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 8.1Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(medium)
- EPSS
- 83.4%
- KEV
- Not listed
Published
January 23, 2017
Last Modified
May 13, 2026
References (6)
- cve@mitrehttp://www.openwall.com/lists/oss-security/2016/05/25/4
- cve@mitrehttp://www.openwall.com/lists/oss-security/2016/05/26/2
- cve@mitrehttps://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2016-013/
- af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2016/05/25/4
- af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2016/05/26/2
- af854a3a-2127-422b-91ae-364da2661108https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2016-013/
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| typo3/cms-extbase | 8.1.1 | — | — |
Frequently asked(5)
What is CVE-2016-5091?
CVE-2016-5091 is a high vulnerability published on January 23, 2017. Extbase in TYPO3 4.3.0 before 6.2.24, 7.x before 7.6.8, and 8.1.1 allows remote attackers to obtain sensitive information or possibly execute arbitrary code via a crafted Extbase action.
When was CVE-2016-5091 disclosed?
CVE-2016-5091 was first published in the National Vulnerability Database on January 23, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-5091 actively exploited?
CVE-2016-5091 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 83.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-5091?
CVE-2016-5091 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2016-5091?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-5091, 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-5091
Is Your Infrastructure Affected by CVE-2016-5091?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.