Reported vulnerability

WordPress Core 2.5.0 - 7.1.4 - Unauthenticated Stored Cross-Site Scripting via Escaped Shortcode Attributes in Comments

Published 18 Nov 2026

Updated 19 Nov 2026

Compare your installed software with the affected versions below. Follow the source’s remediation guidance and test an available update after taking a backup. A database entry describes a reported issue; it does not establish whether a particular website has been compromised.

Does this affect my version?

Check your installed version against this advisory. This compares the report’s version ranges and does not scan your website.

WordPress

In WordPress, open Dashboard > Updates to find your installed WordPress version.

Wordfence advisory

high · CVSS 7.2

WordPress Core is vulnerable to stored cross-site scripting through escaped shortcode attributes in comments in versions 2.5.0 through 7.1.4. An unauthenticated commenter can submit hex or octal escapes that pass comment markup filtering and are later decoded into HTML structural characters by shortcode_parse_atts(). On WordPress 5.0 and later, an approved comment displayed by the Core Latest Comments block can reach the normal shortcode pass; a crafted stock caption and video shortcode chain causes bundled MediaElement code to reconstruct and execute an image event handler from a track label. Earlier versions require another integration that processes comment content as shortcodes and exposes the decoded attribute to an HTML or browser-side sink. The comment must be approved and rendered.

Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

WordPress

Software
WordPress Core · wordpress
Affected versions
From 2.5.0, through 4.6.30; From 4.7.0, through 4.7.39; From 4.8.0, through 4.8.34; From 4.9.0, through 4.9.35; From 5.0.0, through 5.0.31; From 5.1.0, through 5.1.28; From 5.2.0, through 5.2.30; From 5.3.0, through 5.3.27; From 5.4.0, through 5.4.25; From 5.5.0, through 5.5.24; From 5.6.0, through 5.6.23; From 5.7.0, through 5.7.21; From 5.8.0, through 5.8.19; From 5.9.0, through 5.9.20; From 6.0.0, through 6.0.18; From 6.1.0, through 6.1.16; From 6.2.0, through 6.2.15; From 6.3.0, through 6.3.14; From 6.4.0, through 6.4.14; From 6.5.0, through 6.5.14; From 6.6.0, through 6.6.11; From 6.7.0, through 6.7.11; From 6.8.0, through 6.8.12; From 6.9.0, through 6.9.11; From 7.0.0, through 7.0.8; From 7.1.0, through 7.1.4
Fix availability
Fix available
Fixed versions
4.7.40, 4.8.35, 4.9.36, 5.0.32, 5.1.29, 5.2.31, 5.3.28, 5.4.26, 5.5.25, 5.6.24, 5.7.22, 5.8.20, 5.9.21, 6.0.19, 6.1.17, 6.2.16, 6.3.15, 6.4.15, 6.5.15, 6.6.12, 6.7.12, 6.8.13, 6.9.12, 7.0.9, 7.1.5

Recommended action

Update to one of the following versions, or a newer patched version: 4.7.40, 4.8.35, 4.9.36, 5.0.32, 5.1.29, 5.2.31, 5.3.28, 5.4.26, 5.5.25, 5.6.24, 5.7.22, 5.8.20, 5.9.21, 6.0.19, 6.1.17, 6.2.16, 6.3.15, 6.4.15, 6.5.15, 6.6.12, 6.7.12, 6.8.13, 6.9.12, 7.0.9, 7.1.5

Further references (1)
Data sources and licences

Copyright 2012-2026 Defiant Inc.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Read licence terms

Source: Wordfence

Need help fixing this issue?

Get help checking your site, applying an available update and resolving any problems after updating.

Get help with this issue

Questions about this vulnerability

Which versions of WordPress are affected?

Wordfence lists these affected versions: From 2.5.0, through 4.6.30; From 4.7.0, through 4.7.39; From 4.8.0, through 4.8.34; From 4.9.0, through 4.9.35; From 5.0.0, through 5.0.31; From 5.1.0, through 5.1.28; From 5.2.0, through 5.2.30; From 5.3.0, through 5.3.27; From 5.4.0, through 5.4.25; From 5.5.0, through 5.5.24; From 5.6.0, through 5.6.23; From 5.7.0, through 5.7.21; From 5.8.0, through 5.8.19; From 5.9.0, through 5.9.20; From 6.0.0, through 6.0.18; From 6.1.0, through 6.1.16; From 6.2.0, through 6.2.15; From 6.3.0, through 6.3.14; From 6.4.0, through 6.4.14; From 6.5.0, through 6.5.14; From 6.6.0, through 6.6.11; From 6.7.0, through 6.7.11; From 6.8.0, through 6.8.12; From 6.9.0, through 6.9.11; From 7.0.0, through 7.0.8; From 7.1.0, through 7.1.4. Use the version checker above to compare your installed release with this report.

Is a fix available for WordPress?

Wordfence reports a fix for this issue in WordPress. It lists these fixed versions: 4.7.40, 4.8.35, 4.9.36, 5.0.32, 5.1.29, 5.2.31, 5.3.28, 5.4.26, 5.5.25, 5.6.24, 5.7.22, 5.8.20, 5.9.21, 6.0.19, 6.1.17, 6.2.16, 6.3.15, 6.4.15, 6.5.15, 6.6.12, 6.7.12, 6.8.13, 6.9.12, 7.0.9, 7.1.5. Back up your website and test the recommended update before applying it to your live site.

Where can I find my installed WordPress version?

In WordPress, open Dashboard > Updates to find your installed WordPress version.

Does an affected version mean my website has been hacked?

An affected version means the installed release matches a vulnerability described in this report. It does not show whether anyone has exploited it on your website. The checker compares version numbers with stored reports; it does not inspect your website.

Accessibility settings

Adjust how this site looks and moves. Your choices are saved in this browser.