{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-11627 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-11627 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-11627 is a medium-severity vulnerability in sminozzi Site Checkup Debug AI Troubleshooting with Wizard and Tips for Each Issue, published on 30 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-11627 and fix it if it is affected.\n\nWhat it is: CVE-2025-11627 is a medium-severity vulnerability in sminozzi Site Checkup Debug AI Troubleshooting with Wizard and Tips for Each Issue, published on 30 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-11627 in the wild and no public exploit code.\n\nAffected product: sminozzi Site Checkup Debug AI Troubleshooting with Wizard and Tips for Each Issue. 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-11627/ (Markdown: https://insights.sbomify.com/CVE-2025-11627/index.md)","id":"CVE-2025-11627","markdown":"https://insights.sbomify.com/CVE-2025-11627/index.md","name":"CVE-2025-11627","record":{"aliases":["GHSA-95fm-5hch-ccgx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can poison log files to exhaust disk space, causing denial of service in the Site Checkup WordPress plugin.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-117","name":"Improper Output Neutralization for Logs"}],"description":"The Site Checkup Debug AI Troubleshooting with Wizard and Tips for Each Issue plugin for WordPress is vulnerable to log file poisoning in all versions up to, and including, 1.47. This makes it possible for unauthenticated attackers to insert arbitrary content into log files, and potentially cause denial of service via disk space exhaustion.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-03-23","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-03-23T14:49:55Z","kind":"github_poc","ref":"https://github.com/jFriedli/CVE-2025-11627","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"Site Checkup AI Troubleshooting with Wizard and Tips for Each Issue \u003c= 1.47 - Unauthenticated Log File Poisoning","id":"CVE-2025-11627","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"jimit105 Project-Online-Shopping-Website Product Inventory delete.php sql injection","id":"CVE-2025-11628"},"packages":[],"prev":{"headline":"Loop with Unreachable Exit Condition ('Infinite Loop') in Wireshark","id":"CVE-2025-11626"},"products":["Site Checkup Debug AI Troubleshooting with Wizard and Tips for Each Issue"],"published":"2025-10-30","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["sminozzi"]},"summary":"Unauthenticated attackers can poison log files to exhaust disk space, causing denial of service in the Site Checkup WordPress plugin.","url":"https://insights.sbomify.com/CVE-2025-11627/"}