{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-41875 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-41875 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-41875 is a medium-severity missing authorization vulnerability in wpdirectorykit.com WP Directory Kit, published on 13 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-41875 and fix it if it is affected.\n\nWhat it is: CVE-2023-41875 is a medium-severity missing authorization vulnerability in wpdirectorykit.com WP Directory Kit, published on 13 Dec 2024. 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-2023-41875 in the wild and no public exploit code.\n\nAffected product: wpdirectorykit.com WP Directory Kit. 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-41875/ (Markdown: https://insights.sbomify.com/CVE-2023-41875/index.md)","id":"CVE-2023-41875","markdown":"https://insights.sbomify.com/CVE-2023-41875/index.md","name":"CVE-2023-41875","record":{"aliases":["GHSA-689c-7x7v-4xm7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can bypass access controls in WP Directory Kit to perform unauthorized actions due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"wp_directory_kit","vendor":"wpdirectorykit"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Missing Authorization vulnerability in wpdirectorykit.com WP Directory Kit allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Directory Kit: from n/a through 1.2.6.","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":"WordPress WP Directory Kit plugin \u003c= 1.2.6 - Broken Access Control vulnerability","id":"CVE-2023-41875","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress WP Gallery Metabox Plugin \u003c= 1.0.0 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-41876"},"packages":[],"prev":{"headline":"WordPress Order Delivery Date for WooCommerce Plugin \u003c= 3.20.0 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-41874"},"products":["WP Directory Kit"],"published":"2024-12-13","related":[{"cvss_score":10,"headline":"WP Directory Kit \u003c= 1.4.4 - Authentication Bypass to Privilege Escalation via Account Takeover","id":"CVE-2025-13390","kev_date_added":null,"published":"2025-12-03"},{"cvss_score":9.8,"headline":"WP Directory Kit \u003c= 1.1.9 - Unauthenticated Local File Inclusion via wdk_public_action","id":"CVE-2023-2278","kev_date_added":null,"published":"2023-06-13"},{"cvss_score":8.8,"headline":"WP Directory Kit \u003c= 1.3.0 - Authenticated (Subscriber+) SQL Injection","id":"CVE-2024-3217","kev_date_added":null,"published":"2024-04-05"},{"cvss_score":7.1,"headline":"WordPress WP Directory Kit plugin \u003c= 1.3.5 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-37487","kev_date_added":null,"published":"2024-07-21"},{"cvss_score":7.1,"headline":"WordPress WP Directory Kit plugin \u003c= 1.2.9 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-29774","kev_date_added":null,"published":"2024-03-27"},{"cvss_score":6.5,"headline":"Missing authorization in WP Directory Kit","id":"CVE-2023-2351","kev_date_added":null,"published":"2023-06-13"},{"cvss_score":6.5,"headline":"Missing authorization in WP Directory Kit","id":"CVE-2023-2280","kev_date_added":null,"published":"2023-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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["wpdirectorykit.com"]},"summary":"Attackers can bypass access controls in WP Directory Kit to perform unauthorized actions due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2023-41875/"}