Skip to content
Laskyr

Plugins · reactpress · data as of 2026-11-04

Is ReactPress safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.4.1)

As of 2026-11-04. 2 issues are on record for older versions; version 3.4.1 or newer fixes all of them that state a fix.

Latest version
3.4.1
Last updated
2026-10-23
Active installs
2,000+
Known issues on record
2
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 8.0+

Easily create, build and deploy React apps into your existing WordPress sites. — by rockiger

What to do

  1. Update to the latest version (3.4.1). Anything older than 3.4.1 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get reactpress --field=version shows what you run; wp plugin update reactpress updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 6.4 CVE-2026-92712 · published 2026-09-30

Stored cross-site scripting (XSS) in ReactPress (3.4.0 and older)

Affected
3.4.0 and older
Fixed in
3.4.1 *
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The ReactPress – Create React App for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'permalink' parameter in all versions up to, and including, 3.4.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is possible because the permalink parameter is only passed through sanitize_url(), which does not prevent fetching attacker-controlled remote URLs whose response body — including script tags and event-handler attributes — is written verbatim to disk via file_put_contents().

NVD CVE-2026-92712Wordfence advisoryPlugin source

medium 6.0 CVE-2026-66455 · published 2026-08-13

Missing authorization check in ReactPress (3.4.0 and older)

Affected
3.4.0 and older
Fixed in
3.4.1 *
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Patchstack
Details from the advisory

Subscriber Broken Access Control in ReactPress <= 3.4.0 versions.

NVD CVE-2026-66455Patchstack advisory

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
ReactPress vulnerability status badge
<a href="https://laskyr.com/plugins/reactpress"><img src="https://laskyr.com/plugins/reactpress/badge.svg" alt="ReactPress vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit