GHSA-rpxg-hg79-h8q9 — in2code/lux
CRITICALGHSA-rpxg-hg79-h8q9 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in in2code/lux. EPSS puts its 30-day exploitation probability at 26.1% (98th percentile). A fix is available for in2code/lux — see the affected versions and patch details below.
SQL Injection in typo3 extension "LUX - TYPO3 Marketing Automation"
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-rpxg-hg79-h8q9 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
in2code/lux🐘in2code/luxReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
A SQL injection issue was discovered in the lux extension before 17.6.1, and 18.x through 24.x before 24.0.2, for TYPO3.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | in2code/lux | ≥ 18.0.0&&< 24.0.2 | 24.0.2composer require in2code/lux:^24.0.2 |
| 🐘Packagist | in2code/lux | all versions | 17.6.1composer require in2code/lux:^17.6.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for in2code/lux, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update in2code/lux to 24.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rpxg-hg79-h8q9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rpxg-hg79-h8q9 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-rpxg-hg79-h8q9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-rpxg-hg79-h8q9 in your dependencies?
O3 Security finds GHSA-rpxg-hg79-h8q9 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.