Quick answers
- Is CVE-2026-6252 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6252 being exploited in the wild.
- How severe is CVE-2026-6252?
- Medium severity, with a CVSS score of 6.4, published 14 May 2026.
- Which products and versions are affected?
- Meta Field Block up to, and including, 1.5.2.
- Is there a fix for CVE-2026-6252?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-6252 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-6252?
- Check whether you run Meta Field Block at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Meta Field Block plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) due to insufficient input sanitization and output escaping on the 'tagName' block attribute. An authenticated attacker with contributor-level permissions or higher can exploit this by injecting malicious JavaScript into the block settings. Because the 'tagName' attribute is not properly validated, the script is stored in the database and executed in the browser of any user who views the affected page. This vulnerability is present in all versions up to 1.5.2 and was addressed in version 1.5.3.
Affected products
- WordPress plugin Meta Field Block up to, and including, 1.5.2
Timeline
- 2026-05-14: disclosed
- 2026-05-14: advisory