CVE-2022-23799 json
[20220307] - Core - Variable Tampering on JInput $_REQUEST data
published 4y ago modified 2mo ago also BIT-joomla-2022-23799 , EUVD-2022-1302 , GHSA-49fj-qp6p-q544
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
An issue was discovered in Joomla! 4.0.0 through 4.1.0. Under specific circumstances, JInput pollutes method-specific input bags with $_REQUEST data.
Patch / fix
Is CVE-2022-23799 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 FencerExploit prediction
1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| 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 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| OSV | 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 | joomla/input | >=2.0.0, <2.0.2 |
2.0.2 |
| bitnami | joomla | >=4.0.0, <=4.1.0 |
no fix listed |
Affected products
- Joomla! Project Joomla! CMS
- Joomla! Project joomla/input
References
-
github.com
/joomla-framework/input/commit/2086df5860a2edccd77c329ee7cbd118cfe93514
web
-
developer.joomla.org
/security-centre/876-20220307-core-variable-tampering-on-jinput-request-data.html
vendor-advisory, web, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-23799
advisory, web
-
github.com
/joomla/joomla-cms/issues/35541
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/joomla/input/CVE-2022-23799.yaml
web
-
github.com
/joomla-framework/input
package
Sources
- CVE List CVE-2022-23799
- GitHub Advisory GHSA-49fj-qp6p-q544
- NVD CVE-2022-23799
- OSV BIT-joomla-2022-23799
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.