{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2071 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-2071 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-2071 is a medium-severity cross-site scripting vulnerability in Unknown Name Directory, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-2071 and fix it if it is affected.\n\nWhat it is: CVE-2022-2071 is a medium-severity cross-site scripting vulnerability in Unknown Name Directory, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-2071 in the wild and no public exploit code.\n\nAffected product: Unknown Name Directory. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2071/ (Markdown: https://insights.sbomify.com/CVE-2022-2071/index.md)","id":"CVE-2022-2071","markdown":"https://insights.sbomify.com/CVE-2022-2071/index.md","name":"CVE-2022-2071","record":{"aliases":["GHSA-w657-gq68-34f2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can inject malicious scripts via CSRF in the Name Directory plugin, potentially compromising admin accounts.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"name_directory","vendor":"name_directory_project"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Name Directory WordPress plugin before 1.25.4 does not have CSRF check when importing names, and is also lacking sanitisation as well as escaping in some of the imported data, which could allow attackers to make a logged in admin import arbitrary names with XSS payloads in them.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Name Directory \u003c 1.25.4 - Stored Cross-Site Scripting via CSRF","id":"CVE-2022-2071","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Name Directory \u003c 1.25.3 - Reflected Cross-Site Scripting","id":"CVE-2022-2072"},"packages":[],"prev":{"headline":"Grandstream GSD3710 Stack-based Buffer Overflow","id":"CVE-2022-2070"},"products":["Name Directory"],"published":"2022-07-25","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in Name Directory","id":"CVE-2021-20652","kev_date_added":null,"published":"2021-02-05"},{"cvss_score":6.1,"headline":"Name Directory \u003c 1.25.3 - Reflected Cross-Site Scripting","id":"CVE-2022-2072","kev_date_added":null,"published":"2022-07-25"},{"cvss_score":4.3,"headline":"WordPress Name Directory Plugin \u003c= 1.27.1 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-22692","kev_date_added":null,"published":"2023-05-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Unknown"]},"summary":"Attackers can inject malicious scripts via CSRF in the Name Directory plugin, potentially compromising admin accounts.","url":"https://insights.sbomify.com/CVE-2022-2071/"}