{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13920 exists.","fix":"No fix has been published for CVE-2025-13920 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-13920 is a medium-severity vulnerability in wpdirectorykit WP Directory Kit, published on 24 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-13920 and fix it if it is affected.\n\nWhat it is: CVE-2025-13920 is a medium-severity vulnerability in wpdirectorykit WP Directory Kit, published on 24 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13920 exists.\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-2025-13920/ (Markdown: https://insights.sbomify.com/CVE-2025-13920/index.md)","id":"CVE-2025-13920","markdown":"https://insights.sbomify.com/CVE-2025-13920/index.md","name":"CVE-2025-13920","record":{"aliases":["GHSA-7wpw-5pc9-jh59"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can extract email addresses of users with specific roles via the AJAX handler in WP Directory Kit.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The WP Directory Kit plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.4.9 via the wdk_public_action AJAX handler. This makes it possible for unauthenticated attackers to extract email addresses for users with Directory Kit-specific user roles.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2025/CVE-2025-13920.yaml","stars":null,"title":"WP Directory Kit \u003c 1.5.0 - Unauthenticated Email Exposure"}],"tier":"weaponised"},"has_fix":null,"headline":"WP Directory Kit \u003c= 1.4.9 - Unauthenticated Email Exposure via wdk_public_action","id":"CVE-2025-13920","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"weDocs \u003c= 2.1.16 - Missing Authorization to Authenticated (Subscriber+) Documentation Post Update","id":"CVE-2025-13921"},"packages":[],"prev":{"headline":"Component Object Model (COM) Hijacking in Symantec Endpoint Protection Windows Client","id":"CVE-2025-13919"},"products":["WP Directory Kit"],"published":"2026-01-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["wpdirectorykit"]},"summary":"Unauthenticated attackers can extract email addresses of users with specific roles via the AJAX handler in WP Directory Kit.","url":"https://insights.sbomify.com/CVE-2025-13920/"}