{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-5772 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-5772 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-5772 is a medium-severity vulnerability in qriouslad Debug Log Manager – Conveniently Monitor and Inspect Errors, published on 30 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-5772 and fix it if it is affected.\n\nWhat it is: CVE-2023-5772 is a medium-severity vulnerability in qriouslad Debug Log Manager – Conveniently Monitor and Inspect Errors, published on 30 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-5772 in the wild and no public exploit code.\n\nAffected product: qriouslad Debug Log Manager – Conveniently Monitor and Inspect Errors. 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-2023-5772/ (Markdown: https://insights.sbomify.com/CVE-2023-5772/index.md)","id":"CVE-2023-5772","markdown":"https://insights.sbomify.com/CVE-2023-5772/index.md","name":"CVE-2023-5772","record":{"aliases":["GHSA-8mwm-rmq7-g8j8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick administrators into clearing the debug log via forged requests, requiring an upgrade to the Debug Log Manager plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"debug_log_manager","vendor":"bowo"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Debug Log Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.1. This is due to missing or incorrect nonce validation on the clear_log() function. This makes it possible for unauthenticated attackers to clear the debug log via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","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":"Debug Log Manager \u003c= 2.2.0 - Cross-Site Request Forgery","id":"CVE-2023-5772","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"** REJECT ** DO NOT USE THIS CVE RECORD.","id":"CVE-2023-5773"},"packages":[],"prev":{"headline":"HTML injection in AdminUI through email subject","id":"CVE-2023-5771"},"products":["Debug Log Manager – Conveniently Monitor and Inspect Errors"],"published":"2023-11-30","related":[{"cvss_score":7.5,"headline":"Debug Log Manager \u003c 2.3.0 - Sensitive Logs Exposure","id":"CVE-2023-6383","kev_date_added":null,"published":"2024-01-08"},{"cvss_score":5.3,"headline":"WordPress Debug Log Manager Plugin \u003c= 2.3.0 is vulnerable to Sensitive Data Exposure","id":"CVE-2023-6136","kev_date_added":null,"published":"2023-11-30"},{"cvss_score":4.3,"headline":"WordPress Debug Log Manager plugin \u003c= 2.3.1 - Broken Access Control vulnerability","id":"CVE-2024-35669","kev_date_added":null,"published":"2024-06-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-04-08","vendors":["qriouslad"]},"summary":"Attackers can trick administrators into clearing the debug log via forged requests, requiring an upgrade to the Debug Log Manager plugin.","url":"https://insights.sbomify.com/CVE-2023-5772/"}