CVE-2024-1745

Testimonial Slider <= 2.3.6 - Missing Authorization to Authenticated (Author+) Settings Update

2024-03-05 00:00
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 2.3.7
Affected Version
<= 2.3.6
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-1745
View all Testimonial – Testimonial Slider and Showcase Plugin vulnerabilities

At a glance

CVE-2024-1745 is a medium-severity Missing Authorization vulnerability in the Testimonial WordPress plugin, affecting versions <= 2.3.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.3.7; sites on affected versions should update now. Disclosed March 2024, reported by Dmitrii Ignatyev.

Vulnerability Overview

The Testimonial Slider plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the tssSettingsUpdate() function in all versions up to, and including, 2.3.6. This makes it possible for authenticated attackers, with author-level access and above, to update the plugin's settings.

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

Testimonial <= 2.3.6 carries this weakness at tssSettingsUpdate(), and reaching it takes an account at Author 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 Testimonial the fix is 2.3.7: builds <= 2.3.6 are affected, anything from 2.3.7 onward is not.

Remediation

Update to version 2.3.7, 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: Testimonial 2.3.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Other vulnerabilities in Testimonial – Testimonial Slider and Showcase Plugin

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