# CVE-2025-53371: DiscordNotifications allows DOS, SSRF, and possible RCE through requests to user-controlled URLs

> Attackers can trigger SSRF and DoS via arbitrary URLs in DiscordNotifications, potentially leading to remote code execution.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2025
- **Updated:** 10 Jul 2025
- **Also known as:** GHSA-gvfx-p3h5-qf65

## What is CVE-2025-53371?

CVE-2025-53371 is a critical server-side request forgery vulnerability in miraheze DiscordNotifications, published on 10 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

DiscordNotifications is an extension for MediaWiki that sends notifications of actions in your Wiki to a Discord channel. DiscordNotifications allows sending requests via curl and file_get_contents to arbitrary URLs set via $wgDiscordIncomingWebhookUrl and $wgDiscordAdditionalIncomingWebhookUrls. This allows for DOS by causing the server to read large files. SSRF is also possible if there are internal unprotected APIs that can be accessed using HTTP POST requests, which could also possibly lead to RCE. This vulnerability is fixed in commit 1f20d850cbcce5b15951c7c6127b87b927a5415e.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-53371?


## How do I fix CVE-2025-53371?

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

## Is CVE-2025-53371 being exploited?

There is no known exploitation of CVE-2025-53371 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53371 and fix it if it is affected.

What it is: CVE-2025-53371 is a critical server-side request forgery vulnerability in miraheze DiscordNotifications, published on 10 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53371 in the wild and no public exploit code.

Affected product: miraheze DiscordNotifications. 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-2025-53371/ (Markdown: https://insights.sbomify.com/CVE-2025-53371/index.md)
```

## Sources

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

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