{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5920 exists.","fix":"No fix has been published for CVE-2025-5920 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-5920 is a high-severity vulnerability in Unknown Sharable Password Protected Posts, published on 4 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-5920 and fix it if it is affected.\n\nWhat it is: CVE-2025-5920 is a high-severity vulnerability in Unknown Sharable Password Protected Posts, published on 4 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-5920 exists.\n\nAffected product: Unknown Sharable Password Protected Posts. 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-5920/ (Markdown: https://insights.sbomify.com/CVE-2025-5920/index.md)","id":"CVE-2025-5920","markdown":"https://insights.sbomify.com/CVE-2025-5920/index.md","name":"CVE-2025-5920","record":{"aliases":["GHSA-c2r3-hccf-qqvp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can access password-protected posts by retrieving the secret key from the REST API.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"private_post_share","vendor":"fabiantodt"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"The Sharable Password Protected Posts before version 1.1.1 allows access to password protected posts by providing a secret key in a GET parameter. However, the key is exposed by the REST API.","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":"Sharable Password Protected Posts \u003c 1.1.1 - Unauthenticated Password Protect Post Access","id":"CVE-2025-5920","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":"SureForms \u003c 1.7.2 - Reflected XSS","id":"CVE-2025-5921"},"packages":[],"prev":{"headline":"Missing authorization in Timetics – Appointment Booking \u0026 Scheduling","id":"CVE-2025-5919"},"products":["Sharable Password Protected Posts"],"published":"2025-07-04","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-08","vendors":["Unknown"]},"summary":"Unauthenticated attackers can access password-protected posts by retrieving the secret key from the REST API.","url":"https://insights.sbomify.com/CVE-2025-5920/"}