GHSA-45wj-jv2h-jwrf: TYPO3 CMS Privilege Escalation and SQL Injection
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: typo3/cms-core (Packagist) 8.7.17, 9.3.2.
Low priority for now. Upgrade to typo3/cms-core (Packagist) 8.7.17, 9.3.2 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: OSV
Failing to properly dissociate system related configuration from user generated configuration, the Form Framework (system extension "form") is vulnerable to SQL injection and Privilege Escalation. Basically instructions can be persisted to a form definition file that were not configured to be modified - this applies to definitions managed using the form editor module as well as direct file upload using the regular file list module. A valid backend user account as well as having system extension form activated are needed in order to exploit this vulnerability.
- Published
- May 30, 2024
- Updated
- Dec 5, 2024
- EPSS
- —
- CWE
- CWE-89
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
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.
Is your version affected? Check itNoroxi 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 |
|---|---|---|
| Packagist | typo3/cms-core | pkg:composer/typo3/cms-core |
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 8.5.0 · before 8.7.17 | 8.7.17 |
| Packagist | typo3/cms-core | from 9.0.0 · before 9.3.2 | 9.3.2 |
Same product
Packagist: all recordsOther highest-scoring records for the same primary product.
- GHSA-cc97-g92w-jm65TYPO3 CMS Insecure Deserialization & Arbitrary Code Execution39Monitor
- GHSA-x428-565f-8xj2TYPO3 Arbitrary Code Execution and Cross-Site Scripting in Backend API35Monitor
- GHSA-f9hr-7cfq-mjg2TYPO3 Arbitrary Code Execution via File List Module35Monitor
Published before and after this one in the same product
- ← EarlierGHSA-gqqf-g5r7-84vfSep 15, 2022 · TYPO3 HTML Sanitizer Bypasses Cross-Site Scripting Protection24Monitor
- ← EarlierGHSA-x4rj-f7m6-42c3May 30, 2024 · TYPO3 CMS Authentication Bypass vulnerability30Monitor
- Later →GHSA-wg8h-gxf4-g4ghMay 30, 2024 · TYPO3 Cross-Site Scripting in Online Media Asset Rendering24Monitor
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 | 8.7.17 | Package registry (OSV) |
| Packagist:typo3/cms-core | 9.3.2 | 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- GHSA-rxc9-f2x6-qh4w0 days apartTYPO3 Security Misconfiguration for Backend User Accounts30Monitor
- GHSA-x4rj-f7m6-42c30 days apartTYPO3 CMS Authentication Bypass vulnerability30Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
osv
Root cause
The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.
The bug in code
The whole CWE-89 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = '" + owner + "'"
);Fixed
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = $1",
[owner]
);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)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Expanding Control over the Operating System from the DatabaseCAPEC-470Very High
- SQL InjectionCAPEC-66likelihood: High · High
- Blind SQL InjectionCAPEC-7likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- github.com/TYPO3-CMS/core/commit/a0a6271dc8f715b5b6859771333d57925dfb63bc
- github.com/TYPO3-CMS/core/commit/e70d7c66110a0919b39bccdfdc73cbfd7f504dfc
- github.com/TYPO3-CMS/core/commit/eddc7635fb3447f0fb69831855f4095de8e12350
- github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/2018-07-12-3.yaml
- github.com/TYPO3-CMS/core
- typo3.org/security/advisory/typo3-core-sa-2018-003
Vendor advisories and official records. Exploit/PoC links are deliberately left out.