CVE-2026-110525VulnerabilityPublished 6 Nov 2026

The MCB WordPress plugin through 1.0.0 does not sanitise or escape request header values before storing them and later

Source GCVE Database

Compare

Authoritative record:CVE-2026-110525· High

Not known to be exploited.

Data as of 6 Nov 2026, 07:33 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-hp42-vhhj-w836

What to do

Affected software

Product	Affected	Fixed in
MCB	Affected <=1.0.0	Fixed in–

AI-suggested

Users should monitor the vendor advisory for updates. Until a fix is available, restrict access to the statistics page to trusted administrators only and consider disabling the plugin if possible to prevent exploitation.

Description

The MCB WordPress plugin up to version 1.0.0 fails to sanitize or escape request header values before storing and displaying them in the administrator statistics grid. This vulnerability allows unauthenticated attackers to inject malicious JavaScript, which executes in the browser of an administrator viewing the statistics page.

Impact

An unauthenticated attacker can inject malicious JavaScript that executes in the administrator's browser when viewing the statistics page. This could lead to session hijacking, privilege escalation, or other malicious actions performed with administrator privileges.

Summary

The MCB WordPress plugin through version 1.0.0 contains a stored cross-site scripting (XSS) vulnerability due to improper sanitization and escaping of request header values. These values are stored and later rendered in the administrator statistics grid without adequate filtering, enabling unauthenticated attackers to inject and execute arbitrary JavaScript in the context of an administrator's browser session.

References

Community reviews

Loading reviews…