Skip to content
Fencer Intel
critical 9.8

CVE-2022-35628 in the critical feed json

SQL Injection in typo3 extension "LUX - TYPO3 Marketing Automation"

published 4y ago modified 4mo ago also GHSA-rpxg-hg79-h8q9 , EUVD-2022-6412

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
26.8%
EPSS 26.8% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist in2code/lux 17.6.1, 24.0.2
  • in2code living_user_experience 17.6.1, 24.0.2

Is CVE-2022-35628 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

26.82% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist in2code/lux
>=18.0.0, <24.0.2
<17.6.1
24.0.2
17.6.1

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.