{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-2280 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-2280 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-2280 is a medium-severity missing authorization vulnerability in wpdirectorykit WP Directory Kit, published on 9 Jun 2023. 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-2280 and fix it if it is affected.\n\nWhat it is: CVE-2023-2280 is a medium-severity missing authorization vulnerability in wpdirectorykit WP Directory Kit, published on 9 Jun 2023. 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-2280 in the wild and no public exploit code.\n\nAffected product: wpdirectorykit 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-2280/ (Markdown: https://insights.sbomify.com/CVE-2023-2280/index.md)","id":"CVE-2023-2280","markdown":"https://insights.sbomify.com/CVE-2023-2280/index.md","name":"CVE-2023-2280","record":{"aliases":["GHSA-82jf-v4r3-p624"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can modify settings, delete data, and install arbitrary plugins due to missing capability checks in WP Directory Kit.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_directory_kit","vendor":"wpdirectorykit"}],"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-862","name":"Missing Authorization"}],"description":"The WP Directory Kit plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to a missing capability check on the 'ajax_public' function in versions up to, and including, 1.2.2. This makes it possible for unauthenticated attackers to delete or change plugin settings, import demo data, delete Directory Kit related posts and terms, and install arbitrary plugins. A partial patch was introduced in version 1.2.0 and an additional partial patch was introduced in version 1.2.2, but the issue was not fully patched until 1.2.3.","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":"Missing authorization in WP Directory Kit","id":"CVE-2023-2280","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Archiving a team broadcasts unsanitized data over WebSockets","id":"CVE-2023-2281"},"packages":[],"prev":{"headline":"Cross-site request forgery in WP Directory Kit","id":"CVE-2023-2279"},"products":["WP Directory Kit"],"published":"2023-06-09","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"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["wpdirectorykit"]},"summary":"Unauthenticated attackers can modify settings, delete data, and install arbitrary plugins due to missing capability checks in WP Directory Kit.","url":"https://insights.sbomify.com/CVE-2023-2280/"}