Reported vulnerability

WordPress Core < 6.2.1 - Shortcode Execution in User Generated Content

Q: Which versions of WordPress are affected?

Wordfence lists these affected versions: From 5.9, before 5.9.6; From 6.0, before 6.0.4; From 6.1, before 6.1.2; From 6.2, before 6.2.1. Use the version checker above to compare your installed release with this report.

Q: Is a fix available for WordPress?

Wordfence reports a fix for this issue in WordPress. It lists these fixed versions: 5.9.6, 6.0.4, 6.1.2, 6.2.1. Back up your website and test the recommended update before applying it to your live site.

Q: Where can I find my installed WordPress version?

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

Published 19 May 2023

Updated 22 Jan 2024

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.

Wordfence advisory

medium · CVSS 6.5

WordPress Core processes shortcodes in user-generated content on block themes in versions up to, and including, 6.2. This could allow unauthenticated attackers to execute shortcodes via submitting comments or other content, allowing them to exploit vulnerabilities that typically require Subscriber or Contributor-level permissions. While this is likely to have minimal impact on its own, it can significantly increase the severity of other vulnerabilities.

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

WordPress

Software: WordPress Core · wordpress
Affected versions: From 5.9, before 5.9.6; From 6.0, before 6.0.4; From 6.1, before 6.1.2; From 6.2, before 6.2.1
Fix availability: Fix available
Fixed versions: 5.9.6, 6.0.4, 6.1.2, 6.2.1

Recommended action

Update to one of the following versions, or a newer patched version: 5.9.6, 6.0.4, 6.1.2, 6.2.1

Further references (1)

wordfence.com/threat-intel/vulnerabilities/id/6300c8c2-f539-46b2-9ee0-80bebbe4cad3?source=api-prod

Data sources and licences

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 5.9, before 5.9.6; From 6.0, before 6.0.4; From 6.1, before 6.1.2; From 6.2, before 6.2.1. 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: 5.9.6, 6.0.4, 6.1.2, 6.2.1. 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.

These reports cover at least one of the same plugins, themes or WordPress core. Check each report’s affected versions separately.

Back to vulnerability database