{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-25003 exists.","fix":"No fix has been published for CVE-2021-25003 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-25003 is a critical vulnerability in Unknown WPCargo Track \u0026 Trace, published on 14 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-2021-25003 and fix it if it is affected.\n\nWhat it is: CVE-2021-25003 is a critical vulnerability in Unknown WPCargo Track \u0026 Trace, published on 14 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-25003 exists.\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-2021-25003/ (Markdown: https://insights.sbomify.com/CVE-2021-25003/index.md)","id":"CVE-2021-25003","markdown":"https://insights.sbomify.com/CVE-2021-25003/index.md","name":"CVE-2021-25003","record":{"aliases":["GHSA-8pgh-m49h-qpxh"],"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":"Unauthenticated attackers can upload PHP files to the web server, leading to remote code execution in the WPCargo Track \u0026 Trace plugin.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wpcargo_track_\\\u0026_trace","vendor":"wptaskforce"}],"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":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"},{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"The WPCargo Track \u0026 Trace WordPress plugin before 6.9.0 contains a file which could allow unauthenticated attackers to write a PHP file anywhere on the web server, leading to RCE","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-06-26","github_poc":1,"max_poc_stars":6,"metasploit":0,"nuclei":1,"refs":[{"date":"2022-06-26T13:07:47Z","kind":"github_poc","ref":"https://github.com/biulove0x/CVE-2021-25003","stars":6,"title":"WPCargo \u003c 6.9.0 - Unauthenticated RCE"},{"date":null,"kind":"nuclei","ref":"http/cves/2021/CVE-2021-25003.yaml","stars":null,"title":"WordPress WPCargo Track \u0026 Trace \u003c6.9.0 - Remote Code Execution"}],"tier":"weaponised"},"has_fix":null,"headline":"WPCargo \u003c 6.9.0 - Unauthenticated RCE","id":"CVE-2021-25003","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"SEUR Oficial \u003c 1.7.2 - Admin+ Arbitrary File Download","id":"CVE-2021-25004"},"packages":[],"prev":{"headline":"Tipsacarrier \u003c 1.5.0.5 - Unauthenticated Orders Disclosure","id":"CVE-2021-25002"},"products":["WPCargo Track \u0026 Trace"],"published":"2022-03-14","related":[],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Unknown"]},"summary":"Unauthenticated attackers can upload PHP files to the web server, leading to remote code execution in the WPCargo Track \u0026 Trace plugin.","url":"https://insights.sbomify.com/CVE-2021-25003/"}