CVE-2026-6256: Credits Shortcode (WordPress plugin) · Cross-site Scripting
Affects Credits Shortcode (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 May 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| jashjacobCredits Shortcode | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, administrators should restrict contributor-level access to trusted users only and consider disabling or removing the Credits Shortcode plugin if it is not essential. Monitoring for unusual activity related to shortcode usage may help detect exploitation attempts.
Description
The Credits Shortcode plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the 'link' attribute of its 'credits' shortcode. This vulnerability affects all versions up to and including 1.2 and allows authenticated users with contributor-level access or higher to inject malicious scripts. These scripts execute whenever any user views the affected page. The vulnerability arises from insufficient input sanitization and output escaping of user-supplied attributes. The CVSS score is 6.4, indicating a medium severity risk. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.
References
- wordfence.com/threat-intel/vulnerabilities/id/bbe7beae-2803-463c-83ad-5a58c4a55a65?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/source-shortcode/tags/1.2/credits_shortcode.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/source-shortcode/trunk/credits_shortcode.php (opens in a new tab)