# CVE-2023-22493: RSSHub is vulnerable to SSRF (Server-Side Request Forgery)

> Attackers can exploit SSRF in RSSHub to send arbitrary HTTP requests from the server, potentially accessing sensitive internal network resources.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Jan 2023
- **Updated:** 10 Mar 2025
- **Also known as:** GHSA-64wp-jh9p-5cg2

## What is CVE-2023-22493?

CVE-2023-22493 is a high-severity server-side request forgery vulnerability in DIYgod RSSHub, published on 13 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

RSSHub is an open source RSS feed generator. RSSHub is vulnerable to Server-Side Request Forgery (SSRF) attacks. This vulnerability allows an attacker to send arbitrary HTTP requests from the server to other servers or resources on the network. An attacker can exploit this vulnerability by sending a request to the affected routes with a malicious URL. An attacker could also use this vulnerability to send requests to internal or any other servers or resources on the network, potentially gain access to sensitive information that would not normally be accessible and amplifying the impact of the attack. The patch for this issue can be found in commit a66cbcf.

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

## Which versions are affected by CVE-2023-22493?

2 open source packages ship an affected version, including rsshub. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rsshub` | npm | All versions | 1.0.0-master.a66cbcf |
| `rsshub` | npm | All versions | 1.0.0-master.a66cbcf |

Products: Rsshub Rsshub.

## How do I fix CVE-2023-22493?

Upgrade rsshub to 1.0.0-master.a66cbcf or later.

## Is CVE-2023-22493 being exploited?

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

Public exploit code:

- Phân tích CVE-2023-22493 (github_poc): https://github.com/buitanhung144/SSRF-CVE-2023-22493

## Other vulnerabilities in DIYgod RSSHub

- [CVE-2021-21278](https://insights.sbomify.com/CVE-2021-21278/): Risk of code injection in RSSHub (high 8.6)
- [CVE-2024-27927](https://insights.sbomify.com/CVE-2024-27927/): RSSHub vulnerable to SSRF in /mastodon, /zjoi, and /m4 (medium 6.5)
- [CVE-2024-27926](https://insights.sbomify.com/CVE-2024-27926/): RSSHub Cross-site Scripting vulnerability caused by internal media proxy (medium 6.1)
- [CVE-2023-26491](https://insights.sbomify.com/CVE-2023-26491/): RSSHub is vulnerable to cross-site scripting (XSS) via unvalidated URL parameters (medium 5.4)
- [CVE-2022-31110](https://insights.sbomify.com/CVE-2022-31110/): Denial of Service (DoS) vulnerability in RSSHub (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22493 and fix it if it is affected.

What it is: CVE-2023-22493 is a high-severity server-side request forgery vulnerability in DIYgod RSSHub, published on 13 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22493 exists.

Affected packages and fixed versions:
- rsshub (npm): affected all versions; fixed in 1.0.0-master.a66cbcf
- rsshub (npm): affected all versions; fixed in 1.0.0-master.a66cbcf

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-2023-22493/ (Markdown: https://insights.sbomify.com/CVE-2023-22493/index.md)
```

## Sources

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

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