CVE-2025-24580

12 Step Meeting List <= 3.16.5 - Missing Authorization to Authenticated (Contributor+) Arbitrary Content Deletion

2025-01-24 00:00
Kévin Mosbahi (Mika)

Strategic Overview

Status
Patched in 3.16.6
Affected Plugin
12 Step Meeting List
Affected Version
<= 3.16.5
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-24580
View all 12 Step Meeting List vulnerabilities

At a glance

CVE-2025-24580 is a medium-severity Missing Authorization vulnerability in the 12 Step Meeting List WordPress plugin, affecting versions <= 3.16.5. 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.16.6; sites on affected versions should update now. Disclosed January 2025, reported by Kévin Mosbahi (Mika).

Vulnerability Overview

The 12 Step Meeting List plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the wp_ajax_tsml_delete() function in all versions up to, and including, 3.16.5. This makes it possible for authenticated attackers, with Contributor-level access and above, to delete all meeting data.

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

12 Step Meeting List <= 3.16.5 carries this weakness at wp_ajax_tsml_delete(), 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 12 Step Meeting List the fix is 3.16.6: builds <= 3.16.5 are affected, anything from 3.16.6 onward is not.

Remediation

Update to version 3.16.6, 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: 12 Step Meeting List 3.16.6 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-24580https://www.wordfence.com/threat-intel/vulnerabilities/id/d504c2bd-d6a8-4a66-a650-4a18cb32c54ahttps://nvd.nist.gov/vuln/detail/CVE-2025-24580

Related records

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