LiveActive security incident?Get immediate response
CVE Record

CVE-2022-23799: [20220307] - Core - Variable Tampering on JInput $_REQUEST data

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Joomla versions 4.0.0 through 4.1.0 can mix request data into method-specific input handling under specific circumstances. In business terms, code that expects a value only from one request source may receive attacker-controlled data from another source. The source bundle does not provide severity, CVSS, or a confirmed impact chain.

Executive priority

Treat this as an inventory and update-control priority rather than a confirmed emergency. Internet-facing Joomla 4.0.x to 4.1.0 systems should be checked promptly because request tampering can undermine application logic, but the source bundle lacks severity and exploitation evidence.

Technical view

CVE-2022-23799 is a Joomla JInput variable tampering issue where $_REQUEST data can pollute method-specific input bags. Affected products are Joomla CMS 4.0.0-4.1.0 and joomla/input 2.0.0-2.0.1. The available sources do not identify a CWE, CVSS score, fixed version, exploit chain, or affected component-specific preconditions.

Likely exposure

Exposure is likely limited to Joomla 4.0.0-4.1.0 deployments or applications directly using joomla/input 2.0.0-2.0.1. Risk depends on application or extension code that trusts method-specific JInput data for security-sensitive decisions.

Exploitation context

The provided sources do not state active exploitation, and the CVE is not marked KEV. The vendor description indicates abuse requires specific circumstances. No exploit details, payloads, or confirmed real-world attacks are provided in the source bundle.

Researcher notes

The key research gap is impact specificity. Sources only state $_REQUEST pollution into method-specific input bags under specific circumstances. Validation should focus on code paths where GET, POST, COOKIE, or other method-specific data boundaries are security-relevant. Do not assume remote code execution or authentication bypass without product-specific evidence.

Mitigation direction

  • Identify all Joomla CMS instances and their installed versions.
  • Identify direct dependency usage of joomla/input 2.0.0 or 2.0.1.
  • Follow Joomla vendor advisory guidance for fixed versions or mitigations.
  • Prioritize internet-facing Joomla sites handling authentication, forms, or state changes.
  • Review extensions that depend on method-specific request input handling.

Validation and detection

  • Confirm whether Joomla CMS version is between 4.0.0 and 4.1.0.
  • Confirm whether joomla/input version is 2.0.0 or 2.0.1.
  • Review custom code using JInput method-specific input bags.
  • Check whether request parameters influence authorization, routing, or privileged state changes.
  • Document compensating controls if vendor remediation cannot be applied immediately.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-23799 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Joomla! ProjectJoomla! CMS4.0.0-4.1.0Listed
Joomla! Projectjoomla/input2.0.0-2.0.1Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.