CVE-2024-13518

Simple:Press <= 6.10.12 - Cross-Site Request Forgery to Unauthorized Post Editing

2025-02-28 15:24
20kilograma

Strategic Overview

Status
Patched in 6.10.13
Affected Plugin
Simple:Press Forum
Affected Version
<= 6.10.12
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-13518
View all Simple:Press Forum vulnerabilities

At a glance

CVE-2024-13518 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Simple:Press Forum WordPress plugin, affecting versions <= 6.10.12. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.10.13; sites on affected versions should update now. Disclosed February 2025, reported by 20kilograma.

Vulnerability Overview

The Simple:Press Forum plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.10.12. This is due to missing or incorrect nonce validation on the 'sp_save_edited_post' function. This makes it possible for unauthenticated attackers to modify a forum post via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Simple:Press Forum <= 6.10.12 carries this weakness at sp_save_edited_post, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Simple:Press Forum the fix is 6.10.13: builds <= 6.10.12 are affected, anything from 6.10.13 onward is not.

Remediation

Update to version 6.10.13, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Simple:Press Forum: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Simple:Press Forum 6.10.13 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-13518https://www.wordfence.com/threat-intel/vulnerabilities/id/4484fa86-5878-426d-92b9-8eb0751075e5https://nvd.nist.gov/vuln/detail/CVE-2024-13518

Related records

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