{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-2277 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-2277 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-2277 is a medium-severity vulnerability in wpdirectorykit WP Directory Kit, published on 13 Jun 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-2277 and fix it if it is affected.\n\nWhat it is: CVE-2023-2277 is a medium-severity vulnerability in wpdirectorykit WP Directory Kit, published on 13 Jun 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-2277 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-2277/ (Markdown: https://insights.sbomify.com/CVE-2023-2277/index.md)","id":"CVE-2023-2277","markdown":"https://insights.sbomify.com/CVE-2023-2277/index.md","name":"CVE-2023-2277","record":{"aliases":["GHSA-hgfm-xg4h-rcg4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick admins into updating settings and injecting malicious JavaScript via CSRF in WP Directory Kit.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_directory_kit","vendor":"wpdirectorykit"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WP Directory Kit plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.1.9. This is due to missing or incorrect nonce validation on the 'insert' function. This makes it possible for unauthenticated attackers to update the plugin's settings and inject malicious JavaScript 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":"WP Directory Kit \u003c= 1.1.9 - Cross-Site Request Forgery to Stored Cross-Site Scripting via wdk_resultitem","id":"CVE-2023-2277","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"WP Directory Kit \u003c= 1.1.9 - Unauthenticated Local File Inclusion via wdk_public_action","id":"CVE-2023-2278"},"packages":[],"prev":{"headline":"Auth bypass in WCFM Membership – WooCommerce Memberships for Multivendor Marketplace","id":"CVE-2023-2276"},"products":["WP Directory Kit"],"published":"2023-06-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-08","vendors":["wpdirectorykit"]},"summary":"Attackers can trick admins into updating settings and injecting malicious JavaScript via CSRF in WP Directory Kit.","url":"https://insights.sbomify.com/CVE-2023-2277/"}