{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-11244 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-11244 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-11244 is a low-severity authentication bypass vulnerability in saadiqbal Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content, published on 25 Oct 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-11244 and fix it if it is affected.\n\nWhat it is: CVE-2025-11244 is a low-severity authentication bypass vulnerability in saadiqbal Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content, published on 25 Oct 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-11244 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-11244/ (Markdown: https://insights.sbomify.com/CVE-2025-11244/index.md)","id":"CVE-2025-11244","markdown":"https://insights.sbomify.com/CVE-2025-11244/index.md","name":"CVE-2025-11244","record":{"aliases":["GHSA-qpv7-hgm5-vr7r"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can bypass site authorization by spoofing IP headers if the transients feature is enabled, allowing unauthorized access to protected content.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","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-285","name":"Improper Authorization"}],"description":"The Password Protected plugin for WordPress is vulnerable to authorization bypass via IP address spoofing in all versions up to, and including, 2.7.11. This is due to the plugin trusting client-controlled HTTP headers (such as X-Forwarded-For, HTTP_CLIENT_IP, and similar headers) to determine user IP addresses in the `pp_get_ip_address()` function when the \"Use transients\" feature is enabled. This makes it possible for attackers to bypass authorization by spoofing these headers with the IP address of a legitimately authenticated user, granted the \"Use transients\" option is enabled (non-default configuration) and the site is not behind a CDN or reverse proxy that overwrites these headers.","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":"Password Protected \u003c= 2.7.11 - Unauthenticated Authorization Bypass via IP Address Spoofing","id":"CVE-2025-11244","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Insufficient Granularity of Access Control in GitLab","id":"CVE-2025-11246"},"packages":[],"prev":{"headline":"Allocation of Resources Without Limits or Throttling in Shelly Pro 4PM","id":"CVE-2025-11243"},"products":["Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content"],"published":"2025-10-25","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":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["saadiqbal"]},"summary":"Attackers can bypass site authorization by spoofing IP headers if the transients feature is enabled, allowing unauthorized access to protected content.","url":"https://insights.sbomify.com/CVE-2025-11244/"}