CVE-2025-14426

Strong Testimonials <= 3.2.18 - Missing Authorization to Authenticated (Contributor+) Rating Meta Update

2025-12-29 00:00
type5afe

Strategic Overview

Status
Patched in 3.2.19
Affected Plugin
Strong Testimonials
Affected Version
<= 3.2.18
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-14426
View all Strong Testimonials vulnerabilities

At a glance

CVE-2025-14426 is a medium-severity Missing Authorization vulnerability in the Strong Testimonials WordPress plugin, affecting versions <= 3.2.18. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.2.19; sites on affected versions should update now. Disclosed December 2025, reported by type5afe.

Vulnerability Overview

The Strong Testimonials plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check in the 'edit_rating' function in all versions up to, and including, 3.2.18. This makes it possible for authenticated attackers with Contributor-level access and above to modify or delete the rating meta on any testimonial post, including those created by other users, by reusing a valid nonce obtained from their own testimonial edit screen.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Strong Testimonials <= 3.2.18 carries this weakness at edit_rating, and reaching it takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Strong Testimonials the fix is 3.2.19: builds <= 3.2.18 are affected, anything from 3.2.19 onward is not.

Remediation

Update to version 3.2.19, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Strong Testimonials 3.2.19 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-14426https://www.wordfence.com/threat-intel/vulnerabilities/id/c83f48dd-9070-412d-b911-98581a81e29ahttps://nvd.nist.gov/vuln/detail/CVE-2025-14426

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C