CVE-2019-25216: The Rich Review plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the POST body 'update' p

Q: How do I fix CVE-2019-25216?

rich review: upgrade to newer than 1.7.4. Exact commands for each OS are on this page.

Q: Is CVE-2019-25216 being exploited?

CVE-2019-25216 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-25216 affect?

CVE-2019-25216 affects rich review. Severity is high (CVSS 7.2). The Rich Review plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the POST body 'update' parameter in versions up to, and including, 1.7.4 due to insufficient input sanitization and output escaping. This makes it possibl

Q: How urgent is CVE-2019-25216?

Priority 42/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.2REMOTEUPGRADE

CVE-2019-25216 is a high-severity flaw (CVSS 7.2) affecting rich review. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Rich Review plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the POST body 'update' parameter in versions up to, and including, 1.7.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 54%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-10-16
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: starfish

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-10-16 07:15 UTCPublished CVE record published
2026-06-17 02:31 UTCUpdated Record last modified

starfish rich review UPGRADE

Affected: <= 1.7.4

Fixed in: newer than 1.7.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy rich-review || rpm -q rich-review || rich-review --version

2. UPGRADE to newer than 1.7.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade rich-review

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade rich-review

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-25216?

rich review: upgrade to newer than 1.7.4. Exact commands for each OS are on this page.

Is CVE-2019-25216 being exploited?

CVE-2019-25216 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-25216 affect?

CVE-2019-25216 affects rich review. Severity is high (CVSS 7.2). The Rich Review plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the POST body 'update' parameter in versions up to, and including, 1.7.4 due to insufficient input sanitization and output escaping. This makes it possibl

How urgent is CVE-2019-25216?

Priority 42/100. High severity; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs