{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14829 exists.","fix":"No fix has been published for CVE-2025-14829 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14829 is a critical path traversal vulnerability in Unknown E-xact | Hosted Payment |, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-14829 and fix it if it is affected.\n\nWhat it is: CVE-2025-14829 is a critical path traversal vulnerability in Unknown E-xact | Hosted Payment |, published on 13 Jan 2026. 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-2025-14829 exists.\n\nAffected product: Unknown E-xact | Hosted Payment |. 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-2025-14829/ (Markdown: https://insights.sbomify.com/CVE-2025-14829/index.md)","id":"CVE-2025-14829","markdown":"https://insights.sbomify.com/CVE-2025-14829/index.md","name":"CVE-2025-14829","record":{"aliases":["GHSA-q25w-gj9h-7rj6"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can delete arbitrary files on the server via insufficient path validation in the E-xact Hosted Payment WordPress plugin.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[],"description":"The E-xact | Hosted Payment | WordPress plugin through 2.0 is vulnerable to arbitrary file deletion due to insufficient file path validation. This makes it possible for unauthenticated attackers to delete arbitrary files on the server.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"e-xact-hosted-payment \u003c= 2.0 - Unauthenticated Arbitrary File Deletion","id":"CVE-2025-14829","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"JFrog Artifactory Cross-Site Scripting","id":"CVE-2025-14830"},"packages":[],"prev":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2025-14828"},"products":["E-xact | Hosted Payment |"],"published":"2026-01-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["Unknown"]},"summary":"Unauthenticated attackers can delete arbitrary files on the server via insufficient path validation in the E-xact Hosted Payment WordPress plugin.","url":"https://insights.sbomify.com/CVE-2025-14829/"}