CVE
TYPO3 CMS Dashboard server-side request forgery in RSS widget
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
- Exploited
- No known exploitation
- Fix
- Fixed in 14.3.12
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 14.3.12.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
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.
Original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects Packagist packages
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 14.3.12.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- typo3/cms-dashboardPackagist
From 14.0.0 · fixed in 14.3.12
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Patch
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125165
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: cve.now feed data
Which versions are affected by CVE-2026-125165?
typo3/cms-dashboard (Packagist): from 14.0.0 before 14.3.12.Source: cve.now feed data
How do I fix CVE-2026-125165?
Upgrade to a fixed version: 14.3.12.Source: cve.now feed data