CVE-2026-13458: GenerateBlocks (WordPress plugin) · Cross-site Scripting
Affects GenerateBlocks (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 1 Nov 2026, 08:20 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% 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 1 Aug 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 31 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| edge22GenerateBlocks | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict contributor-level access to trusted users only and avoid using dynamic tags in non-URL HTML attributes with untrusted post meta values. Monitor vendor channels for official updates and patches.
Description
The GenerateBlocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Dynamic Tag Injection in HTML Attributes in all versions up to, and including, 2.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. A Contributor-level attacker can store the malicious payload by placing a dynamic tag such as {{post_meta key:...}} in a non-URL HTML attribute (e.g., title, aria-label, alt, or data-* attributes) of a GenerateBlocks element block, then setting the corresponding unprotected post meta key via the Custom Fields metabox to a value containing a closing quote and an injected event-handler attribute.
References
- wordfence.com/threat-intel/vulnerabilities/id/402e10b4-84f0-4f93-a85c-037876d26e58?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/generateblocks/tags/2.3.0/includes/dynamic-tags/class-register-dynamic-tag.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/generateblocks/tags/2.3.0/includes/functions.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/generateblocks/tags/2.3.0/includes/dynamic-tags/class-dynamic-tag-callbacks.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/generateblocks/tags/2.3.0/includes/general.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/generateblocks/tags/2.2.1/includes/dynamic-tags/class-register-dynamic-tag.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/generateblocks/tags/2.2.1/includes/functions.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/generateblocks/tags/2.2.1/includes/dynamic-tags/class-dynamic-tag-callbacks.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/generateblocks/tags/2.2.1/includes/general.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3625942%40generateblocks&new=3625942%40generateblocks (opens in a new tab)