CVE-2024-1446

NextScripts: Social Networks Auto-Poster <= 4.4.3 - Cross-Site Request Forgery to Arbitrary Post Deletion

2024-05-21 18:36
Krzysztof Zając

Strategic Overview

Status
Patched in 4.4.4
Affected Plugin
NextScripts: Social Networks Auto-Poster
Affected Version
<= 4.4.3
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-1446
View all NextScripts: Social Networks Auto-Poster vulnerabilities

At a glance

CVE-2024-1446 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the NextScripts WordPress plugin, affecting versions <= 4.4.3. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.4.4; sites on affected versions should update now. Disclosed May 2024, reported by Krzysztof Zając.

Vulnerability Overview

The NextScripts: Social Networks Auto-Poster plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.4.3. This is due to missing or incorrect nonce validation on the nxssnap-reposter page. This makes it possible for unauthenticated attackers to delete arbitrary posts or pages 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)

Reaching this weakness in NextScripts <= 4.4.3 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 NextScripts the fix is 4.4.4: builds <= 4.4.3 are affected, anything from 4.4.4 onward is not.

Remediation

Update to version 4.4.4, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-1446https://www.wordfence.com/threat-intel/vulnerabilities/id/306b23ee-7dcb-4281-a218-21168998c4b9https://nvd.nist.gov/vuln/detail/CVE-2024-1446

Related records

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