{"answers":{"affected":"2 open source packages ship an affected version, including yeswiki/yeswiki.","exploited":"There is no known exploitation of CVE-2026-52771 in the wild and no public exploit code.","fix":"Upgrade yeswiki/yeswiki to 4.6.6 or later.","what":"CVE-2026-52771 is a high-severity SQL injection vulnerability in yeswiki, published on 4 Sep 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-52771 and fix it if it is affected.\n\nWhat it is: CVE-2026-52771 is a high-severity SQL injection vulnerability in yeswiki, published on 4 Sep 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-52771 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- yeswiki/yeswiki (Packagist): affected from 4.2.0; fixed in 4.6.6\n- yeswiki/yeswiki (Packagist): affected from 4.2.0; 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-52771/ (Markdown: https://insights.sbomify.com/CVE-2026-52771/index.md)","id":"CVE-2026-52771","markdown":"https://insights.sbomify.com/CVE-2026-52771/index.md","name":"CVE-2026-52771","record":{"aliases":["GHSA-8f2v-2qhj-gfwg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"YesWiki wiki system","requires_auth":"low_privilege","summary":"A low-privilege user can execute arbitrary SQL queries via second-order injection in the page delete API, allowing data exfiltration or modification.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"YesWiki is a wiki system written in PHP. From version 4.2.0 to before version 4.6.6, ApiController::deletePage() interpolates a page tag retrieved from the database into a DELETE FROM …_links WHERE to_tag = '$tag' query without escaping. The page tag is attacker-controlled — the POST /api/pages/{tag} API accepts arbitrary URL-encoded values, including single quotes, and stores them. A low-privilege authenticated user can therefore create a page whose tag is a SQL fragment, make the page non-orphaned via the standard {{include page=\"…\"}} link mechanism, and then invoke the delete endpoint to execute arbitrary SQL inside the wiki database - including time-based blind data exfiltration from any table. 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":"none_known"},"has_fix":true,"headline":"YesWiki: Second-Order SQL Injection in Page Delete API via Unescaped Page Tag (`ApiController::deletePage`)","id":"CVE-2026-52771","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"YesWiki has stored XSS in Bazar form-field templates via unescaped field.label / field.hint (|raw('html'))","id":"CVE-2026-52772"},"packages":[{"ecosystem":"Packagist","fixed":["4.6.6"],"introduced":["4.2.0"],"last_affected":[],"package":"yeswiki/yeswiki","purl":null,"source":"GHSA-8f2v-2qhj-gfwg"},{"ecosystem":"Packagist","fixed":["4.6.6"],"introduced":["4.2.0"],"last_affected":[],"package":"yeswiki/yeswiki","purl":"pkg:composer/yeswiki/yeswiki","source":"GHSA-8f2v-2qhj-gfwg"}],"prev":{"headline":"Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in yeswiki/yeswiki","id":"CVE-2026-52770"},"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["YesWiki"]},"summary":"A low-privilege user can execute arbitrary SQL queries via second-order injection in the page delete API, allowing data exfiltration or modification.","url":"https://insights.sbomify.com/CVE-2026-52771/"}