cve.bz

CVE-2026-118530 Incorrect Authorization

5.0 mediumEPSS 0.2%

Medium (5.0). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
The Directorist: AI-Powered Business Directory, Listings & Classified Ads WordPress plugin before 8.11 does not check that the acting user may edit each targeted user when handling an email-verification bulk action on multisite, allowing an Administrator of one site on the network to lock out users of other sites, including the network Super Administrator, until they re-verify their email.

Severity

CVSS 3.1

5.0 medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 12th 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: no · Technical impact: partial, assessed 2026-11-07. 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-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-118530 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118530?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118530?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-118530 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-118530

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-118530](https://cve.bz/cve/badge/CVE-2026-118530.svg)](https://cve.bz/cve/CVE-2026-118530)

HTML:

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

History

  1. The NVD deferred its analysis

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

References

Check your stackJSON