{"answers":{"affected":"3 open source packages ship an affected version, including joomla/input and joomla. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23799 in the wild and no public exploit code.","fix":"Upgrade joomla/input to 2.0.2 or later.","what":"CVE-2022-23799 is a critical vulnerability in Joomla Joomla\\!, published on 30 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-23799 and fix it if it is affected.\n\nWhat it is: CVE-2022-23799 is a critical vulnerability in Joomla Joomla\\!, published on 30 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-23799 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- joomla/input (Packagist): affected from 2.0.0; fixed in 2.0.2\n- joomla/input (Packagist): affected from 2.0.0; fixed in 2.0.2\n- joomla (Bitnami): affected from 4.0.0 up to 4.1.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-23799/ (Markdown: https://insights.sbomify.com/CVE-2022-23799/index.md)","id":"CVE-2022-23799","markdown":"https://insights.sbomify.com/CVE-2022-23799/index.md","name":"CVE-2022-23799","record":{"aliases":["BIT-joomla-2022-23799","GHSA-49fj-qp6p-q544"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Joomla CMS","requires_auth":"none","summary":"Attackers can tamper with input data in Joomla CMS due to improper handling of request variables, potentially altering application state or accessing data.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Joomla","cpe":[{"product":"joomla\\!","vendor":"joomla"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"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.","ecosystems":["Bitnami","Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"[20220307] - Core - Variable Tampering on JInput $_REQUEST data","id":"CVE-2022-23799","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"joomla:joomla\\!","products":["joomla:joomla\\!"],"type":"other","year":"2022"},"n_packages":3,"n_references":1,"next":{"headline":"[20220308] - Core - Inadequate content filtering within the filter code","id":"CVE-2022-23800"},"packages":[{"ecosystem":"Bitnami","fixed":[],"introduced":["4.0.0"],"last_affected":["4.1.0"],"package":"joomla","purl":"pkg:bitnami/joomla","source":"BIT-joomla-2022-23799"},{"ecosystem":"Packagist","fixed":["2.0.2"],"introduced":["2.0.0"],"last_affected":[],"package":"joomla/input","purl":null,"source":"GHSA-49fj-qp6p-q544"},{"ecosystem":"Packagist","fixed":["2.0.2"],"introduced":["2.0.0"],"last_affected":[],"package":"joomla/input","purl":"pkg:composer/joomla/input","source":"GHSA-49fj-qp6p-q544"}],"prev":{"headline":"[20220306] - Core - Inadequate validation of internal URLs","id":"CVE-2022-23798"},"products":["Joomla! CMS","joomla/input"],"published":"2022-03-30","related":[{"cvss_score":9.8,"headline":"PHPMailer Command Injection","id":"CVE-2016-10033","kev_date_added":"2025-07-07","published":"2016-12-30"},{"cvss_score":5.3,"headline":"Joomla! Improper Access Control","id":"CVE-2023-23752","kev_date_added":"2024-01-08","published":"2023-02-16"},{"cvss_score":9.8,"headline":"Joomla! Core - [20260518] - Transport encryption downgrade for password and username reset links","id":"CVE-2026-48902","kev_date_added":null,"published":"2026-05-26"},{"cvss_score":9.8,"headline":"[20250401] - Joomla Framework - SQL injection vulnerability in quoteNameStr method of Database package","id":"CVE-2025-25226","kev_date_added":null,"published":"2025-04-08"},{"cvss_score":9.8,"headline":"[20220303] - Core - User row are not bound to a authentication mechanism","id":"CVE-2022-23795","kev_date_added":null,"published":"2022-03-30"},{"cvss_score":9.8,"headline":"[20220305] - Core - Inadequate filtering on the selected Ids","id":"CVE-2022-23797","kev_date_added":null,"published":"2022-03-30"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-02-25","vendors":["Joomla! Project"]},"summary":"Attackers can tamper with input data in Joomla CMS due to improper handling of request variables, potentially altering application state or accessing data.","url":"https://insights.sbomify.com/CVE-2022-23799/"}