# CVE-2022-41495: Server-side request forgery in n/a

> An attacker can exploit an SSRF vulnerability in ClipperCMS to make arbitrary requests from the server, potentially accessing internal resources.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2022
- **Updated:** 15 May 2025
- **Also known as:** GHSA-qp2p-m8v3-mghg

## What is CVE-2022-41495?

CVE-2022-41495 is a critical server-side request forgery vulnerability in n/a, published on 13 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ClipperCMS 1.3.3 was discovered to contain a Server-Side Request Forgery (SSRF) via the rss_url_news parameter at /manager/index.php.

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

## Which versions are affected by CVE-2022-41495?

It affects 1 product.


Products: Clippercms Clippercms.

## How do I fix CVE-2022-41495?

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

## Is CVE-2022-41495 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-41497](https://insights.sbomify.com/CVE-2022-41497/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2018-19135](https://insights.sbomify.com/CVE-2018-19135/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-11571](https://insights.sbomify.com/CVE-2018-11571/): Other in n/a (high 8.8)
- [CVE-2018-19424](https://insights.sbomify.com/CVE-2018-19424/): File upload in n/a (high 7.2)
- [CVE-2018-12101](https://insights.sbomify.com/CVE-2018-12101/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41495 and fix it if it is affected.

What it is: CVE-2022-41495 is a critical server-side request forgery vulnerability in n/a, published on 13 Oct 2022. 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-2022-41495 exists.

Affected product: n/a. 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-2022-41495/ (Markdown: https://insights.sbomify.com/CVE-2022-41495/index.md)
```

## Sources

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

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