CVE-2024-27954

Automatic <= 3.92.0 - Unauthenticated Arbitrary File Download and Server-Side Request Forgery

2024-03-13 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 3.92.1
Affected Plugin
WordPress Automatic Plugin
Affected Version
<= 3.92.0
CVSS
9.8Critical
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2024-27954
View all WordPress Automatic Plugin vulnerabilities

At a glance

CVE-2024-27954 is a critical-severity Server-Side Request Forgery (SSRF) vulnerability in the WordPress Automatic Plugin WordPress plugin, affecting versions <= 3.92.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.92.1; sites on affected versions should update now. Disclosed March 2024, reported by Rafie Muhammad.

Vulnerability Overview

The WordPress Automatic Plugin plugin for WordPress is vulnerable to Server-Side Request Forgery and Arbitrary File Downloads in all versions up to, and including, 3.92.0. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services in addition to accessing arbitrary files on the server that may contain sensitive information.

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, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in WordPress Automatic Plugin <= 3.92.0 takes no account at all. 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 WordPress Automatic Plugin the fix is 3.92.1: builds <= 3.92.0 are affected, anything from 3.92.1 onward is not.

Remediation

Update to version 3.92.1, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WordPress Automatic Plugin 3.92.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-27954https://www.wordfence.com/threat-intel/vulnerabilities/id/620e8931-64f0-4d9c-9a4c-1f5a703845ffhttps://nvd.nist.gov/vuln/detail/CVE-2024-27954

Related records

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