{"answers":{"affected":"2 open source packages ship an affected version, including yeswiki/yeswiki.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52767 exists.","fix":"Upgrade yeswiki/yeswiki to 4.6.6 or later.","what":"CVE-2026-52767 is a high-severity vulnerability in yeswiki, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-52767 and fix it if it is affected.\n\nWhat it is: CVE-2026-52767 is a high-severity vulnerability in yeswiki, published on 4 Sep 2026. 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-2026-52767 exists.\n\nAffected packages and fixed versions:\n- yeswiki/yeswiki (Packagist): affected from 4.6.2; fixed in 4.6.6\n- yeswiki/yeswiki (Packagist): affected from 4.6.2; fixed in 4.6.6\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-52767/ (Markdown: https://insights.sbomify.com/CVE-2026-52767/index.md)","id":"CVE-2026-52767","markdown":"https://insights.sbomify.com/CVE-2026-52767/index.md","name":"CVE-2026-52767","record":{"aliases":["GHSA-mv28-wj57-f57g"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"YesWiki","requires_auth":"none","summary":"Attackers can bypass ActivityPub signature verification in YesWiki by exploiting PHP truthiness rules, allowing unauthenticated processing of malicious payloads.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"YesWiki is a wiki system written in PHP. From version 4.6.2 to before version 4.6.6, HttpSignatureService::verifySignature() checks the result of PHP's openssl_verify() with a loose boolean negation - if (!openssl_verify(...)) { throw ... }. PHP's openssl_verify has four possible return values: 1, 0, -1, and \"false\". The -1 row is the bypass: PHP's truthiness rules make -1 a truthy value, so !(-1) === false, the throw is skipped, and the controller proceeds to processActivity(). Any condition that makes OpenSSL's EVP_VerifyFinal() return -1 triggers the bypass. The reachable consequence is the controller silently treats a failed verification as success and processes the attacker's payload. This issue has been patched in version 4.6.6.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"YesWiki: Unauthenticated ActivityPub Signature-Verification Bypass via `!openssl_verify(...)` accepting `int(-1)`","id":"CVE-2026-52767","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"YesWiki: Unauthenticated Server-Side Request Forgery via ActivityPub `Signature.keyId`","id":"CVE-2026-52769"},"packages":[{"ecosystem":"Packagist","fixed":["4.6.6"],"introduced":["4.6.2"],"last_affected":[],"package":"yeswiki/yeswiki","purl":null,"source":"GHSA-mv28-wj57-f57g"},{"ecosystem":"Packagist","fixed":["4.6.6"],"introduced":["4.6.2"],"last_affected":[],"package":"yeswiki/yeswiki","purl":"pkg:composer/yeswiki/yeswiki","source":"GHSA-mv28-wj57-f57g"}],"prev":{"headline":"YesWiki: Unauthenticated arbitrary page deletion via `{{erasespamedcomments}}` action","id":"CVE-2026-52766"},"products":["yeswiki"],"published":"2026-09-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["YesWiki"]},"summary":"Attackers can bypass ActivityPub signature verification in YesWiki by exploiting PHP truthiness rules, allowing unauthenticated processing of malicious payloads.","url":"https://insights.sbomify.com/CVE-2026-52767/"}