{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-0385 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-0385 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-0385 is a medium-severity vulnerability in kunalnagar Custom 404 Pro, published on 18 Jan 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-0385 and fix it if it is affected.\n\nWhat it is: CVE-2023-0385 is a medium-severity vulnerability in kunalnagar Custom 404 Pro, published on 18 Jan 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-0385 in the wild and no public exploit code.\n\nAffected product: kunalnagar Custom 404 Pro. 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-0385/ (Markdown: https://insights.sbomify.com/CVE-2023-0385/index.md)","id":"CVE-2023-0385","markdown":"https://insights.sbomify.com/CVE-2023-0385/index.md","name":"CVE-2023-0385","record":{"aliases":["GHSA-r65v-776h-88pg"],"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":"Unauthenticated attackers can trick administrators into deleting logs via forged requests in the Custom 404 Pro WordPress plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"custom_404_pro","vendor":"kunalnagar"}],"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 Custom 404 Pro plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.7.1. This is due to missing or incorrect nonce validation on the custom_404_pro_admin_init function. This makes it possible for unauthenticated attackers to delete logs, via 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":"Custom 404 Pro \u003c= 3.7.1 - Cross-Site Request Forgery","id":"CVE-2023-0385","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Linux Kernel Improper Ownership Management","id":"CVE-2023-0386"},"packages":[],"prev":{"headline":"Uncontrolled Resource Consuption in M-Files Server","id":"CVE-2023-0384"},"products":["Custom 404 Pro"],"published":"2023-01-18","related":[{"cvss_score":9.8,"headline":"Custom 404 Pro \u003c 3.8.1 - Multiple SQL Injection","id":"CVE-2023-2032","kev_date_added":null,"published":"2023-06-27"},{"cvss_score":8.3,"headline":"WordPress Custom 404 Pro Plugin \u003c= 3.7.0 is vulnerable to SQL Injection (SQLi)","id":"CVE-2022-47605","kev_date_added":null,"published":"2023-04-12"},{"cvss_score":7.1,"headline":"WordPress Custom 404 Pro plugin \u003c= 3.11.1 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-39646","kev_date_added":null,"published":"2024-08-01"},{"cvss_score":7.1,"headline":"WordPress Custom 404 Pro Plugin \u003c= 3.10.0 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-51540","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":6.1,"headline":"Custom 404 Pro \u003c 3.7.3 - Reflected Cross-Site Scripting","id":"CVE-2023-2023","kev_date_added":null,"published":"2023-05-30"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-15838","kev_date_added":null,"published":"2019-08-30"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-14789","kev_date_added":null,"published":"2019-08-15"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["kunalnagar"]},"summary":"Unauthenticated attackers can trick administrators into deleting logs via forged requests in the Custom 404 Pro WordPress plugin.","url":"https://insights.sbomify.com/CVE-2023-0385/"}