{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54352 exists.","fix":"No fix has been published for CVE-2025-54352 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-54352 is a low-severity vulnerability in WordPress, published on 21 Jul 2025. 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-54352 and fix it if it is affected.\n\nWhat it is: CVE-2025-54352 is a low-severity vulnerability in WordPress, published on 21 Jul 2025. 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-54352 exists.\n\nAffected product: WordPress. 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-54352/ (Markdown: https://insights.sbomify.com/CVE-2025-54352/index.md)","id":"CVE-2025-54352","markdown":"https://insights.sbomify.com/CVE-2025-54352/index.md","name":"CVE-2025-54352","record":{"aliases":["DEBIAN-CVE-2025-54352","GHSA-585c-5qcq-7fgc","UBUNTU-CVE-2025-54352"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress CMS","requires_auth":"none","summary":"Remote attackers can guess titles of private and draft posts via XML-RPC pingback requests, exposing sensitive content metadata.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-669","name":"Incorrect Resource Transfer Between Spheres"}],"description":"WordPress 3.5 through 6.8.2 allows remote attackers to guess titles of private and draft posts via pingback.ping XML-RPC requests. NOTE: the Supplier is not changing this behavior.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-07-28","github_poc":3,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-07-28T13:22:02Z","kind":"github_poc","ref":"https://github.com/yohannslm/CVE-2025-54352","stars":1,"title":"CVE-2025-54352 PoC"},{"date":"2025-10-08T04:00:38Z","kind":"github_poc","ref":"https://github.com/limmmw/CVE-2025-54352","stars":0,"title":null},{"date":"2025-11-27T06:30:44Z","kind":"github_poc","ref":"https://github.com/mufasa-noir/XMLRPC-Pingback-vulnerability-POC","stars":0,"title":"This is my own written POC on the xmlrpc-pingback vulnerabiity found on wordpress. CVE-2025-54352."}],"tier":"weaponised"},"has_fix":false,"headline":"Information disclosure in WordPress","id":"CVE-2025-54352","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in FortiSandbox","id":"CVE-2025-54353"},"packages":[],"prev":{"headline":"Memory corruption in iperf3","id":"CVE-2025-54351"},"products":["WordPress"],"published":"2025-07-21","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-21","vendors":["WordPress"]},"summary":"Remote attackers can guess titles of private and draft posts via XML-RPC pingback requests, exposing sensitive content metadata.","url":"https://insights.sbomify.com/CVE-2025-54352/"}