# CVE-2024-27954: WordPress Automatic plugin <= 3.92.0 - Unauthenticated Arbitrary File Download and SSRF vulnerability

> Unauthenticated attackers can exploit path traversal to download arbitrary files and perform server-side request forgery in the WP Automatic plugin.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-cjr8-gj3h-wpfp

## What is CVE-2024-27954?

CVE-2024-27954 is a critical path traversal vulnerability in WP Automatic Automatic, published on 17 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WP Automatic Automatic allows Path Traversal, Server Side Request Forgery.This issue affects Automatic: from n/a through 3.92.0.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-27954?


## How do I fix CVE-2024-27954?

No fix has been published for CVE-2024-27954 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-27954 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27954 exists.

Public exploit code:

- Automatic Plugin for WordPress < 3.92.1 Multiples Vulnerabilities (github_poc): https://github.com/gh-ost00/CVE-2024-27954
- https://github.com/babydessy/CVE-2024-27954 (github_poc): https://github.com/babydessy/CVE-2024-27954
- https://github.com/r0otk3r/CVE-2024-27954 (github_poc): https://github.com/r0otk3r/CVE-2024-27954
- WordPress Automatic Plugin <3.92.1 - Arbitrary File Download and SSRF (nuclei): http/cves/2024/CVE-2024-27954.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-27954 and fix it if it is affected.

What it is: CVE-2024-27954 is a critical path traversal vulnerability in WP Automatic Automatic, published on 17 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27954 exists.

Affected product: WP Automatic Automatic. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-27954/ (Markdown: https://insights.sbomify.com/CVE-2024-27954/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-27954
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-27954
- OSV: https://osv.dev/vulnerability/CVE-2024-27954

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-27954/
Summaries are generated and may contain mistakes; the official description above is the record.