How severe is CVE-2022-35628?

CVE-2022-35628 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-35628?

CVE-2022-35628 affects the following packages: in2code/lux (Packagist), in2code/lux (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-35628?

Update in2code/lux to 24.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-35628 is resolved across your whole dependency graph.

How do I detect CVE-2022-35628 in my Packagist dependencies?

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.

How do I mitigate CVE-2022-35628 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2022-35628 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-35628 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-35628?

CVE-2022-35628 has an EPSS (Exploit Prediction Scoring System) score of 26.8%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2022-35628?

CVE-2022-35628 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-35628 published, and has it been updated?

CVE-2022-35628 was published on July 12, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2022-35628 — lux

CRITICAL

CVE-2022-35628 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in in2code/lux. EPSS puts its 30-day exploitation probability at 26.8% (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"

Also known asGHSA-rpxg-hg79-h8q9

Published

Jul 12, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

26.8%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘in2code/lux🐘in2code/lux

Real-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

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`in2code/lux`	≥ 18.0.0&&< 24.0.2	24.0.2`composer require in2code/lux:^24.0.2`
🐘Packagist	`in2code/lux`	all versions	17.6.1`composer require in2code/lux:^17.6.1`

Affected Products

1 product · 2 configurations

Application

living user experiencein2code

≥ 18.0.0 && < 24.0.2

range

Detection & mitigation playbook

Open-source dependency

Detect
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 CVE-2022-35628 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2022-35628 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-89SQL Injection

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jul 12, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-35628

GHSA-rpxg-hg79-h8q9

References

Advisorygithub.com · CVE 2022 35628.json Advisorynvd.nist.gov · CVE 2022 35628 Advisorytypo3.org · typo3 ext sa 2022 014 Webgithub.com · CVE 2022 35628.yaml

Related vulnerabilities

This CVE is critical severity; 1 of 8 other CVEs with CWE-89 is rated as high or higher (top: critical).

CVE-2026-44265CVE-2026-33944CVE-2026-115324CVE-2026-107375CVE-2026-107385CVE-2026-107384CVE-2026-60090CVE-2026-62251Browse all CWE-89

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-35628 — lux

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-35628 in your dependencies?