Joomla\!Application · Joomla
CVE-2022-23799
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in Joomla! 4.0.0 through 4.1.0. Under specific circumstances, JInput pollutes method-specific input bags with $_REQUEST data.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Joomla! 4.0.0 through 4.1.0, the JInput class improperly allows $_REQUEST data to contaminate method-specific input bags (e.g., GET-only or POST-only data). This breaks the separation between HTTP methods and can allow attackers to inject input parameters where they should be filtered out, potentially bypassing input validation and access controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Joomla\!Application
>= 4.0.0, <= 4.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Joomla versionLocate the version.php file in your Joomla installation (typically at /libraries/src/Version.php or check the administrator manifest.xml) and read the VERSION constant to determine the installed version.Affected if The installed version is between 4.0.0 and 4.1.0 inclusive.
-
Identify JInput usage in custom codeSearch your custom extensions and templates for usage of JInput or the CMS\Application\CMSApplication::input method. Look for code that calls get method on specific input sources like $app->input->get or $app->input->post, and check if logic depends on the separation between GET, POST, and REQUEST data.Affected if Custom extensions use JInput and depend on GET-only or POST-only data remaining isolated from other HTTP method inputs.
-
Review input validation logicExamine PHP files in your Joomla installation (particularly in /components/ and /modules/) for input validation or access control logic that relies on method-specific input. Look for conditions that check $input->get->get() or $input->post->get() assuming these only contain data from their respective HTTP methods.Affected if The application contains validation logic that assumes GET and POST data are strictly separated, which could be bypassed.
-
Audit API endpointsReview any REST API endpoints or form handlers in custom extensions that process user input. Check if they explicitly filter input by method (e.g., only accepting POST data) and whether they perform authorization checks based on input values.Affected if API endpoints accept input from multiple HTTP methods and perform access control based on that input.
You are affected if your Joomla installation runs version 4.0.0 through 4.1.0 AND your site uses custom extensions or logic that relies on JInput maintaining strict separation between HTTP methods.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Joomla! to version 4.1.1 or later. Review custom extensions that rely on JInput to ensure they do not depend on the vulnerable behavior and continue functioning correctly after the patch.
Joomla! 4.1.1 or later
- Download Joomla! 4.1.1 or later from the official Joomla! downloads page
- Backup your existing Joomla! installation and database
- Upload and extract the Joomla! upgrade package to your server
- Run the Joomla! update process through the Administrator dashboard or command-line
- Verify the update was successful by checking the Joomla! version in the Administrator dashboard
- Clear any cache and test the site's functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Joomla\!
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23799 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data