# CVE-2024-13618: Downloable by American Osteopathic Association <= 0.1.0 - Unauthenticated SSRF

> Unauthenticated attackers can exploit the aoa-downloadable WordPress plugin to make arbitrary server-side requests, potentially accessing internal resources.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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:** 25 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-4878-3496-cr5j

## What is CVE-2024-13618?

CVE-2024-13618 is a high-severity server-side request forgery vulnerability in Unknown aoa-downloadable, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The aoa-downloadable WordPress plugin through 0.1.0 lacks authorization and authentication for requests to its download.php endpoint, allowing unauthenticated visitors to make requests to arbitrary URLs.

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

It affects 1 product.


Products: Osteopathic Downloadable by American Osteopathic Association.

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

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

## Is CVE-2024-13618 being exploited?

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

## Other vulnerabilities in Unknown aoa-downloadable

- [CVE-2024-13617](https://insights.sbomify.com/CVE-2024-13617/): Downloable by American Osteopathic Association <= 0.1.0 - Unauthenticated Arbitrary File Download (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13618 is a high-severity server-side request forgery vulnerability in Unknown aoa-downloadable, published on 25 Mar 2025. 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-13618 exists.

Affected product: Unknown aoa-downloadable. 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-13618/ (Markdown: https://insights.sbomify.com/CVE-2024-13618/index.md)
```

## Sources

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

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