cve.bz

CVE-2026-118418 WP Directory Kit < 1.6.3 - Unauthenticated User Data and Contact Message Disclosure

5.3 mediumEPSS 0.3%

Medium (5.3) in unknown wp directory kit. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
The WP Directory Kit WordPress plugin before 1.6.3 does not restrict which database models and columns its public directory-search action may return, nor verify authorisation on it, allowing unauthenticated attackers to read other users' personal data, including email addresses and logins, and private contact-form submissions.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
WPScan (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-118418 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118418?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118418?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118418 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-118418

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-118418](https://cve.bz/cve/badge/CVE-2026-118418.svg)](https://cve.bz/cve/CVE-2026-118418)

HTML:

<a href="https://cve.bz/cve/CVE-2026-118418"><img src="https://cve.bz/cve/badge/CVE-2026-118418.svg" alt="CVE-2026-118418"></a>

Affected

  • unknown:wp directory kit

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

History

  1. The NVD deferred its analysis
  2. Scored 5.3 medium

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON