CVE-2023-47127: Weak Authentication in Session Handling in typo3/cms-core
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.56% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: typo3/cms-core (Packagist) 10.4.41, 11.5.33, 12.4.8.
Low priority for now. Upgrade to typo3/cms-core (Packagist) 10.4.41, 11.5.33, 12.4.8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
TYPO3 is an open source PHP based web content management system released under the GNU GPL. In typo3 installations there are always at least two different sites. Eg. first.example.org and second.example.com. In affected versions a session cookie generated for the first site can be reused on the second site without requiring additional authentication. This vulnerability has been addressed in versions 8.7.55, 9.5.44, 10.4.41, 11.5.33, and 12.4.8. Users are advised to upgrade. There are no known workarounds for this vulnerability.
- Published
- Nov 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 46th percentile
- CWE
- CWE-302
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.4
- CNA · GitHub_M
- 4.2
- 1.2 point gap
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| typo3 | typo3 | cpe:2.3:a:typo3:typo3 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- typo3 typo38.0.0 and later · before 8.7.55
- typo3 typo39.0.0 and later · before 9.5.44
- typo3 typo310.0.0 and later · before 10.4.41
- typo3 typo311.0.0 and later · before 11.5.33
- typo3 typo312.0.0 and later · before 12.4.8
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
TYPO3 typo3
- >= 8.0.0, < 8.7.55, >= 9.0.0, < 9.5.44, >= 10.0.0, < 10.4.41, >= 11.0.0, < 11.5.33, >= 12.0.0, < 12.4.8affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | typo3/cms-core | from 10.0.0 · before 10.4.41 | 10.4.41 |
| Packagist | typo3/cms-core | from 11.0.0 · before 11.5.33 | 11.5.33 |
| Packagist | typo3/cms-core | from 12.0.0 · before 12.4.8 | 12.4.8 |
| Packagist | typo3/cms-core | from 8.0.0 · before 8.7.55 | 8.7.55 |
| Packagist | typo3/cms-core | from 9.0.0 · before 9.5.44 | 9.5.44 |
Same product
typo3: all recordsOther highest-scoring records for the same primary product.
- CVE-2009-0255The System extension Install tool in TYPO3 4.0.0 through 4.0.9, 4.1.0 through 4.1.7, and 4.2.0 through 4.2.3 creates the encryption key with60This week
- CVE-2013-6288Unspecified vulnerability in the Apache Solr for TYPO3 (solr) extension before 2.8.3 for TYPO3 has unknown impact and remote attack vectors,41Plan
- CVE-2013-5303Unspecified vulnerability in the Store Locator (locator) extension before 3.1.5 for TYPO3 has unknown impact and remote attack vectors, rela41Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-38499Jul 25, 2023 · typo3/cms-core Information Disclosure due to Out-of-scope Site Resolution21Monitor
- ← EarlierCVE-2023-47126Nov 14, 2023 · Information Disclosure in Install Tool in typo3/cms-install21Monitor
- Later →CVE-2023-30451Dec 25, 2023 · In TYPO3 11.5.24, the filelist component allows attackers (who have access to the administrator panel) to read arbitrary files via directory19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:typo3/cms-core | 10.4.41 | Package registry (OSV) |
| Packagist:typo3/cms-core | 11.5.33 | Package registry (OSV) |
| Packagist:typo3/cms-core | 12.4.8 | Package registry (OSV) |
| Packagist:typo3/cms-core | 8.7.55 | Package registry (OSV) |
| Packagist:typo3/cms-core | 9.5.44 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
—
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2024-22188111 days apartTYPO3 before 13.0.1 allows an authenticated admin user (with system maintainer privileges) to execute arbitrary shell commands (with the pri29Monitor
- CVE-2023-3045141 days apartIn TYPO3 11.5.24, the filelist component allows attackers (who have access to the administrator panel) to read arbitrary files via directory19Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-302 · Authentication Bypass by Assumed-Immutable DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- HTTP Verb TamperingCAPEC-274Medium
- Accessing/Intercepting/Modifying HTTP CookiesCAPEC-31likelihood: High · High
- Manipulating Opaque Client-based Data TokensCAPEC-39likelihood: High · Medium
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Manipulating User-Controlled VariablesCAPEC-77likelihood: High · Very High
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.