{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-1436 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-1436 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-1436 is a medium-severity cross-site scripting vulnerability in Unknown WPCargo Track \u0026 Trace, published on 16 May 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-1436 and fix it if it is affected.\n\nWhat it is: CVE-2022-1436 is a medium-severity cross-site scripting vulnerability in Unknown WPCargo Track \u0026 Trace, published on 16 May 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-1436 in the wild and no public exploit code.\n\nAffected product: Unknown WPCargo Track \u0026 Trace. 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-1436/ (Markdown: https://insights.sbomify.com/CVE-2022-1436/index.md)","id":"CVE-2022-1436","markdown":"https://insights.sbomify.com/CVE-2022-1436/index.md","name":"CVE-2022-1436","record":{"aliases":["GHSA-5c5x-7wp7-xwgj"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can execute arbitrary scripts in victim browsers via unsanitized tracking number input in the WPCargo Track \u0026 Trace plugin.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"track_\\\u0026_trace","vendor":"wptaskforce"}],"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-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The WPCargo Track \u0026 Trace WordPress plugin before 6.9.5 does not sanitise and escape the wpcargo_tracking_number parameter before outputting it back in the page, which could allow attackers to perform reflected Cross-Site Scripting attacks.","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":"WPCargo Track \u0026 Trace \u003c 6.9.5 - Reflected Cross Site Scripting","id":"CVE-2022-1436","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Heap-based Buffer Overflow in radareorg/radare2","id":"CVE-2022-1437"},"packages":[],"prev":{"headline":"WPCargo Track \u0026 Trace \u003c 6.9.5 - Admin+ Stored Cross Site Scripting","id":"CVE-2022-1435"},"products":["WPCargo Track \u0026 Trace"],"published":"2022-05-16","related":[{"cvss_score":9.3,"headline":"WordPress WPCargo Track \u0026 Trace plugin \u003c= 8.0.2 - SQL Injection vulnerability","id":"CVE-2024-44004","kev_date_added":null,"published":"2024-09-17"},{"cvss_score":4.8,"headline":"WPCargo Track \u0026 Trace \u003c 6.9.5 - Admin+ Stored Cross Site Scripting","id":"CVE-2022-1435","kev_date_added":null,"published":"2022-05-16"}],"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 execute arbitrary scripts in victim browsers via unsanitized tracking number input in the WPCargo Track \u0026 Trace plugin.","url":"https://insights.sbomify.com/CVE-2022-1436/"}