WordPress myCred plugin <= 4.0.2 - Content Injection vulnerability

published 2026-11-11 22h ago modified 2026-11-11 19h ago also EUVD-2026-123421

cvss: 4.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: —; no EPSS score yet
public exploits: 0; none known

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in myCred myCred mycred allows Code Injection.This issue affects myCred: from n/a through 4.0.2.

Patch / fix

fixed in 1

myCred myCred 4.0.3

Is CVE-2026-125778 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 19h ago (2026-11-11)

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected products

myCred myCred

Classification

Weakness

CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-4-0-2-content-injection-vulnerability-
vdb-entry

Sources

CVE List CVE-2026-125778
NVD CVE-2026-125778

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.