{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-3453 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-3453 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-3453 is a medium-severity vulnerability in saadiqbal Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content, published on 17 Apr 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-3453 and fix it if it is affected.\n\nWhat it is: CVE-2025-3453 is a medium-severity vulnerability in saadiqbal Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content, published on 17 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-3453 in the wild and no public exploit code.\n\nAffected product: saadiqbal Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content. 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-3453/ (Markdown: https://insights.sbomify.com/CVE-2025-3453/index.md)","id":"CVE-2025-3453","markdown":"https://insights.sbomify.com/CVE-2025-3453/index.md","name":"CVE-2025-3453","record":{"aliases":["GHSA-vmhf-wmj5-jx54"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can extract all protected site content if the Use Transient setting is enabled in the Password Protected WordPress plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The Password Protected – Password Protect your WordPress Site, Pages, \u0026 WooCommerce Products – Restrict Content, Protect WooCommerce Category and more plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.7.7 via the 'password_protected_cookie' function. This makes it possible for unauthenticated attackers to extract sensitive data including all protected site content if the 'Use Transient' setting is enabled.","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":"Information disclosure in Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content","id":"CVE-2025-3453","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Grafana's datasource proxy API allows authorization checks to be bypassed","id":"CVE-2025-3454"},"packages":[],"prev":{"headline":"SecuPress Free \u003c= 2.3.9 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Plugin Installation","id":"CVE-2025-3452"},"products":["Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content"],"published":"2025-04-17","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["saadiqbal"]},"summary":"Unauthenticated attackers can extract all protected site content if the Use Transient setting is enabled in the Password Protected WordPress plugin.","url":"https://insights.sbomify.com/CVE-2025-3453/"}