{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-0551 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-0551 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-0551 is a high-severity unsafe deserialization vulnerability in buildwps PPWP – Password Protect Pages, published on 22 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-0551 and fix it if it is affected.\n\nWhat it is: CVE-2026-0551 is a high-severity unsafe deserialization vulnerability in buildwps PPWP – Password Protect Pages, published on 22 Aug 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-2026-0551 in the wild and no public exploit code.\n\nAffected product: buildwps PPWP – Password Protect Pages. 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-2026-0551/ (Markdown: https://insights.sbomify.com/CVE-2026-0551/index.md)","id":"CVE-2026-0551","markdown":"https://insights.sbomify.com/CVE-2026-0551/index.md","name":"CVE-2026-0551","record":{"aliases":["GHSA-fgg6-3rw5-h3j8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can inject PHP objects via deserialization, potentially leading to code execution or data access if a POP chain exists.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","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-502","name":"Deserialization of Untrusted Data"}],"description":"The PPWP – Password Protect Pages plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.9.18 via deserialization of untrusted input from the 'post_protection_roles' vulnerable parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.","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":"PPWP – Password Protect Pages \u003c= 1.9.18 - Authenticated (Contributor+) PHP Object Injection via post_protection_roles","id":"CVE-2026-0551","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in Simple Shopping Cart","id":"CVE-2026-0552"},"packages":[],"prev":{"headline":"myCred \u003c= 2.9.7.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'mycred_load_coupon' Shortcode","id":"CVE-2026-0550"},"products":["PPWP – Password Protect Pages"],"published":"2026-08-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-08-25","vendors":["buildwps"]},"summary":"Authenticated attackers can inject PHP objects via deserialization, potentially leading to code execution or data access if a POP chain exists.","url":"https://insights.sbomify.com/CVE-2026-0551/"}