CVE-2025-9899
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Trust Reviews plugin for Google, Tripadvisor, Yelp, Airbnb and other platforms plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the feed_save function. This makes it possible for unauthenticated attackers to create or modify feed entries via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Trust Reviews WordPress plugin is vulnerable to CSRF in all versions up to 1.0 due to missing nonce validation in the feed_save function. This allows unauthenticated attackers to trick administrators into creating or modifying review feed entries via forged requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Trust Reviews plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Trust Reviews', or check the /wp-content/plugins/ directory for a trust-reviews folder. Note the installed version from the plugin metadata.Affected if The plugin is not installed or has been removed entirely.
-
Verify the installed plugin versionIn Plugins > Installed Plugins, find Trust Reviews and read the version number displayed below the plugin name. Compare this to the affected range: all versions up to and including 1.0.Affected if The installed version is 1.0 or any earlier version (e.g., 0.9, 0.8, etc.).
-
Inspect the feed_save function for nonce validationAccess the plugin source files via file manager or FTP. Navigate to the plugin directory and locate the file containing the feed_save function (commonly in includes/admin or similar). Open the file and search for the feed_save function definition. Look for a wp_verify_nonce() or wp_create_nonce() call within or before this function.Affected if The feed_save function contains no nonce validation check (no wp_verify_nonce() call present).
-
Determine if the site has vulnerable admin endpoints exposedCheck if the WordPress admin area is accessible and whether feed management features exist in the plugin settings. Look for any admin pages under the Trust Reviews menu that handle feed creation or modification.Affected if The plugin admin interface with feed management capabilities is accessible to administrators.
You are affected if the Trust Reviews plugin version is 1.0 or earlier AND the feed_save function lacks wp_verify_nonce() validation, allowing forged requests to modify review feeds.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to a patched version of the plugin that implements proper nonce validation in the feed_save function, or add wp_verify_nonce() check before processing feed_save requests.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9899 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9899 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data