{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-66428 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-66428 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66428 is a high-severity vulnerability in n/a, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66428 and fix it if it is affected.\n\nWhat it is: CVE-2025-66428 is a high-severity vulnerability in n/a, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-66428 in the wild and no public exploit code.\n\nAffected product: n/a. 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-66428/ (Markdown: https://insights.sbomify.com/CVE-2025-66428/index.md)","id":"CVE-2025-66428","markdown":"https://insights.sbomify.com/CVE-2025-66428/index.md","name":"CVE-2025-66428","record":{"aliases":["GHSA-7rjh-m98r-x685"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress Toolkit","requires_auth":"low_privilege","summary":"An attacker can escalate privileges by exploiting improper handling of WordPress directory names in the WebPros WordPress Toolkit.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An issue with WordPress directory names in WebPros WordPress Toolkit before 6.9.1 allows privilege escalation.","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":"Privilege escalation in n/a","id":"CVE-2025-66428","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2025-66429"},"packages":[],"prev":{"headline":"trytond does not enforce access rights for data export","id":"CVE-2025-66424"},"products":["n/a"],"published":"2026-01-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-23","vendors":["n/a"]},"summary":"An attacker can escalate privileges by exploiting improper handling of WordPress directory names in the WebPros WordPress Toolkit.","url":"https://insights.sbomify.com/CVE-2025-66428/"}