GHSA-7qwg-fcpw-xg5g: Privilege Escalation & SQL Injection in TYPO3 CMS
Noroxi assessment
Priority: Monitor (action score 35/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. No special conditions are required; it is repeatable.
- Fixed version: typo3/cms (Packagist) 8.7.17, 9.3.2.
Low priority for now. Upgrade to typo3/cms (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
- Jun 5, 2024
- Updated
- Dec 2, 2024
- EPSS
- —
- CWE
- CWE-94
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 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 | pkg:composer/typo3/cms |
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 | from 8.5.0 · before 8.7.17 | 8.7.17 |
| Packagist | typo3/cms | 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-67wg-6j7r-mqh8Arbitrary Code Execution in TYPO3 CMS39Monitor
- GHSA-gwfx-p7mr-f92vMissing Access Check in TYPO3 CMS36Monitor
- GHSA-8h4m-r4wm-xj7rTYPO3 Arbitrary Code Execution via File List Module35Monitor
Published before and after this one in the same product
- ← EarlierGHSA-8h28-f46f-m87hJun 5, 2024 · Insecure Deserialization in TYPO3 CMS0Monitor
- ← EarlierGHSA-g4pf-3jvq-2gcwJun 5, 2024 · TYPO3 Remote Code Execution in third party library swiftmailer0Monitor
- Later →GHSA-c7p6-3c9c-f88qJun 5, 2024 · Information Disclosure in TYPO3 CMS14Monitor
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 | 8.7.17 | Package registry (OSV) |
| Packagist:typo3/cms | 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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- GHSA-67wg-6j7r-mqh80 days apartArbitrary Code Execution in TYPO3 CMS39Monitor
- GHSA-g4pf-3jvq-2gcw0 days apartTYPO3 Remote Code Execution in third party library swiftmailer0Monitor
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-c5mj-39cf-3pp52 days apartTYPO3 Security Misconfiguration for Backend User Accounts29Monitor
- GHSA-6xh8-8pfv-53vx0 days apartAuthentication Bypass in TYPO3 CMS21Monitor
- GHSA-mh3r-6cp5-hc2j0 days apartAuthentication Bypass in TYPO3 Frontend21Monitor
- GHSA-6f9m-v7mp-7jjq0 days apartAuthentication Bypass in TYPO3 CMS0Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · 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.
- No special conditions are required; it is repeatable.
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
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv
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)
Change log (1)
- 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.