CVE-2023-46641

12 Step Meeting List <= 3.14.24 - Authenticated (Contributor+) Server-Side Request Forgery

2023-11-27 00:00
Shahzaib Ali Khan

Strategic Overview

Status
Patched in 3.14.25
Affected Plugin
12 Step Meeting List
Affected Version
<= 3.14.24
CVSS
6.4Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2023-46641
View all 12 Step Meeting List vulnerabilities

At a glance

CVE-2023-46641 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the 12 Step Meeting List WordPress plugin, affecting versions <= 3.14.24. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.14.25; sites on affected versions should update now. Disclosed November 2023, reported by Shahzaib Ali Khan.

Vulnerability Overview

The 12 Step Meeting List plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.14.24 via the tsml_add_data_source parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in 12 Step Meeting List <= 3.14.24 takes an account at Contributor level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For 12 Step Meeting List the fix is 3.14.25: builds <= 3.14.24 are affected, anything from 3.14.25 onward is not.

Remediation

Update to version 3.14.25, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: 12 Step Meeting List 3.14.25 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-46641https://www.wordfence.com/threat-intel/vulnerabilities/id/4d6e9cb0-6b90-4a5b-8626-0b3f378fbc92https://nvd.nist.gov/vuln/detail/CVE-2023-46641

Related records

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