CVE-2026-93485: WordPress core <= 7.1 - Unauth. Cross Site Scripting (XSS) vulnerability

Published Sep 18, 2026
·
Updated

Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Automattic WordPress core allows DOM-Based XSS.

This issue affects WordPress versions 7.1 before 7.1.1; 7.0 through 7.0.4; 6.9 through 6.9.7; 6.8 through 6.8.8; 6.7 through 6.7.7; 6.6 through 6.6.7; 6.5 through 6.5.10; 6.4 through 6.4.10; 6.3 through 6.3.10; 6.2 through 6.2.11; 6.1 through 6.1.12; 6.0 through 6.0.14; 5.9 through 5.9.16; 5.8 through 5.8.15; 5.7 through 5.7.17; 5.6 through 5.6.19; 5.5 through 5.5.20; 5.4 through 5.4.21; 5.3 through 5.3.23; 5.2 through 5.2.26; 5.1 through 5.1.24; 5.0 through 5.0.27; 4.9 through 4.9.31; 4.8 through 4.8.30; and 4.7 through 4.7.35.

The Unauthenticated Stored XSS vulnerability in the WordPress core can be reproduced on a default WordPress installation. Comment moderation is disabled by default, and the requirement for commenters to have a previously approved comment can be bypassed.

Affected Software

1 affected component
Automattic WordPress core>=4.7<=4.7.35, >=4.8<=4.8.30, >=4.9<=4.9.31, >=5.0<=5.0.27, >=5.1<=5.1.24, >=5.2<=5.2.26, >=5.3<=5.3.23, >=5.4<=5.4.21, >=5.5<=5.5.20, >=5.6<=5.6.19, >=5.7<=5.7.17, >=5.8<=5.8.15, >=5.9<=5.9.16, >=6.0<=6.0.14, >=6.1<=6.1.12, >=6.2<=6.2.11, >=6.3<=6.3.10, >=6.4<=6.4.10, >=6.5<=6.5.10, >=6.6<=6.6.7, >=6.7<=6.7.7, >=6.8<=6.8.8, >=6.9<=6.9.7, >=7.0<=7.0.4, >=7.1<=7.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 7.1.1
  2. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 7.0.5
  3. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 6.9.8
  4. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 6.8.9
  5. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 6.7.8
  6. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 6.6.8
  7. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 6.5.11
  8. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 6.4.11
  9. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 6.3.11
  10. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 6.2.12
  11. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 6.1.13
  12. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 6.0.15
  13. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 5.9.17
  14. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 5.8.16
  15. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 5.7.18
  16. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 5.6.20
  17. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 5.5.21
  18. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 5.4.22
  19. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 5.3.24
  20. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 5.2.27
  21. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 5.1.25
  22. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 5.0.28
  23. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 4.9.32
  24. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 4.8.31
  25. Upgrade

    Upgrade Automattic WordPress core to a version that resolves this vulnerability.

    Fixed in 4.7.36

Event History

Sep 18, 2026
CVE Published
via MITRE·06:00 AM
Data Sourced
via MITRE·06:00 AM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Which installations are exposed by default?

A default WordPress installation is affected if it runs one of the listed vulnerable releases. The issue can be reproduced with the default configuration because comment moderation is disabled by default.

2

Does an attacker need an account or elevated permissions?

No. The vulnerability is described as unauthenticated stored XSS, so an attacker does not need a WordPress account or privileges. Exploitation requires user interaction, as reflected by the UI:R vector.

3

Does requiring previously approved commenters prevent exploitation?

No. The requirement for commenters to have a previously approved comment can be bypassed, so it should not be relied on as a mitigation.

4

Which releases contain fixes?

The affected ranges indicate fixes in WordPress 7.1.1, 7.0.5, 6.9.8, 6.8.9, 6.7.8, 6.6.8, 6.5.11, 6.4.11, 6.3.11, 6.2.12, 6.1.13, 6.0.15, 5.9.17, 5.8.16, 5.7.18, 5.6.20, 5.5.21, 5.4.22, 5.3.24, 5.2.27, 5.1.25, 5.0.28, 4.9.32, 4.8.31, and 4.7.36.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203