CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2025-59021

Traffic Control Gone Rogue: Hijacking TYPO3 Redirects (CVE-2025-59021)

Alon Barad
Alon Barad
Software Engineer

Feb 19, 2026·7 min read·41 visits

Executive Summary (TL;DR)

Restricted TYPO3 backend users can create redirects for *any* domain on the instance, bypassing site-specific permissions. This allows an editor of 'Site A' to redirect traffic from 'Site B' to a malicious target.

A Broken Access Control vulnerability in the TYPO3 CMS 'Redirects' module allows restricted backend users to manipulate redirect rules for domains they are not authorized to manage. By exploiting this flaw, a low-privileged editor with access to the module can hijack traffic from any site hosted on the same TYPO3 instance, facilitating high-impact phishing or SEO poisoning attacks.

The Hook: Who Watches the Traffic Controller?

Multi-tenancy is the bread and butter of enterprise CMS installations. You have one TYPO3 instance hosting the corporate site, the HR portal, the marketing blog, and maybe a few localized landing pages. The security model relies heavily on 'Web Mounts'—invisible fences that keep the HR intern from accidentally nuking the CEO's blog post. It’s a beautiful system, usually.

But here’s the thing about complex systems: eventually, someone adds a feature that decides it's too cool for fences. Enter the Redirects Module. This component is responsible for handling HTTP redirects (301s, 307s) directly within the CMS. Ideally, if I'm an editor for blog.example.com, I should only be able to tell blog.example.com/old-post to go to blog.example.com/new-post.

CVE-2025-59021 reveals that TYPO3 forgot to check the badge at the door. The Redirects module treated permissions with a binary simplicity: 'Do you have access to the module?' If the answer was yes, the system handed you the keys to the entire kingdom's traffic control tower. This isn't just a bug; it's the digital equivalent of giving a valet driver the keys to every car in the parking lot, not just the one they were hired to park.

The Flaw: Logic Gaps in the Authorization Layer

The vulnerability is a classic case of Missing Authorization (CWE-862), specifically manifesting as an Insecure Direct Object Reference (IDOR) on steriods. In TYPO3, permissions are granular. You have table-level permissions (can I edit sys_redirect rows?) and page-tree permissions (can I edit pages under node/123?).

However, redirect records in the sys_redirect table are technically detached from the standard page tree hierarchy. They are records that apply to a domain, but they don't necessarily live under that domain's page ID in a way that inherits the standard permission checks automatically. The code responsible for saving these records checked if the user had write access to the table, but it failed to cross-reference the source_host field of the redirect against the user's allowed Web Mounts.

> [!NOTE] > In a multi-site setup, this is catastrophic. A user restricted to marketing.local could create a rule saying: "If a request comes in for secure-admin.local/login, redirect it to attacker-controlled-site.com/fake-login."

The application logic implicitly trusted that if a user could see the form, they were allowed to modify whatever data they put into it. It’s a failure to validate the semantic validity of the input (the domain ownership) against the user's contextual privileges.

The Code: Patching the Hole

The fix required a significant overhaul of how redirect permissions are calculated. The core team couldn't just add a simple if statement; they had to introduce an entirely new service to map users to hosts.

First, they introduced the SourceHostProvider. This service intersects the site configurations with the user's web mounts to determine exactly which domains a user is legally allowed to touch. Then, they implemented a RedirectPermissionGuard. Here is a simplified look at the logic flow:

Before (Vulnerable Logic):

// DataHandler.php
public function processDatamap() {
    if ($user->check('tables_modify', 'sys_redirect')) {
        // User can write to the table? Great, save it.
        $this->saveRecord($table, $id, $data);
    }
}

After (Patched Logic): The patch introduces a hook into the DataHandler to inspect the payload before saving.

// DataHandlerPermissionGuardHook.php
public function processDatamap_preProcessFieldArray(array $incomingFieldArray, ...): void
{
    // 1. Get the source_host the user is trying to set
    $requestedHost = $incomingFieldArray['source_host'];
 
    // 2. Ask the SourceHostProvider if the user owns this host
    if (!$this->sourceHostProvider->isHostAllowed($user, $requestedHost)) {
        // 3. Yeet the request into the void
        $this->logger->warning('Attempt to modify sys_redirect for unauthorized host');
        throw new AccessDeniedException('You have no power here.');
    }
}

They didn't just stop at the UI (which can be bypassed). They hooked directly into the data persistence layer (DataHandler), ensuring that even if you craft a raw HTTP POST request bypassing the backend interface, the database execution will still be blocked.

The Exploit: Hijacking the Intranet

Let's walk through how a malicious insider—or an attacker who has compromised a low-level editor account—would weaponize this. We assume the attacker has access to the TYPO3 backend and the Redirects module, but is restricted to a minor microsite.

The Setup:

  • Attacker Scope: http://useless-microsite.corp
  • Target Scope: http://intranet.corp
  • Goal: Credential Harvesting.

The Attack Chain:

  1. Recon: The attacker logs in and opens the Redirects module. They see a list of redirects. Even if the list is filtered, the "Create New Redirect" button is active.
  2. Payload Construction: The attacker creates a new record.
    • Source Domain: intranet.corp (The vulnerability allows selecting/entering this manually).
    • Source Path: /hr/payroll-login
    • Target: https://evil-payroll-clone.com
    • Status Code: 307 (Temporary Redirect - less likely to be cached permanently, good for phishing).
  3. Execution: The attacker saves the record. Because the backend code fails to validate that the attacker owns intranet.corp, the record is written to sys_redirect.
  4. Trigger: The next time a legitimate employee visits intranet.corp/hr/payroll-login, the TYPO3 routing engine sees the match and immediately bounces them to the phishing site.

The Impact: Why This Matters

This is a Medium severity CVSS (6.4), but don't let the score fool you. In the hands of a creative attacker, the impact is high. The primary issue is Scope Change (S:C). The vulnerability allows lateral movement from a low-value asset (a microsite) to a high-value asset (the main corporate domain).

Scenarios:

  • Phishing: As described above, redirecting login pages.
  • SEO Poisoning: An attacker could 301 redirect high-ranking pages from the main site to their own gambling or spam sites, effectively stealing the domain's "link juice" and reputation.
  • Denial of Service (Soft): Creating a redirect loop on the homepage (/ redirects to /) effectively taking the main site offline for all visitors.

Because this requires authentication, it's not a "drive-by" exploit. However, in large organizations with hundreds of CMS users, the "Insider Threat" or "Compromised Credential" vector is statistically probable.

The Fix: Remediation Strategy

The remediation is straightforward: Update TYPO3. The patch is available across all supported versions (v10 through v14). Specifically, you are looking for versions 14.0.2, 13.4.23, 12.4.41, 11.5.49, or 10.4.55.

If you cannot patch immediately: You must restrict access to the Redirects module. Go to your Backend User Groups and uncheck the "Redirects" module for everyone except the absolute highest-tier Super Admins who are trusted with the entire installation.

Also, review your current sys_redirect table. Run a SQL query to audit for suspicious cross-domain redirects:

SELECT * FROM sys_redirect 
WHERE source_host NOT IN ('your-primary-domain.com') 
ORDER BY crdate DESC;

If you see redirects for domains created by users who shouldn't be managing those domains, you may have already been targeted.

Official Patches

TYPO3Official Advisory and Patch Download

Fix Analysis (3)

Technical Appendix

CVSS Score
6.4/ 10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
EPSS Probability
0.01%
Top 99% most exploited

Affected Systems

TYPO3 CMS v14.0.0 - 14.0.1TYPO3 CMS v13.0.0 - 13.4.22TYPO3 CMS v12.0.0 - 12.4.40TYPO3 CMS v11.0.0 - 11.5.48TYPO3 CMS v10.0.0 - 10.4.54

Affected Versions Detail

Product
Affected Versions
Fixed Version
TYPO3 CMS
TYPO3 Association
14.0.0 - 14.0.114.0.2
TYPO3 CMS
TYPO3 Association
13.0.0 - 13.4.2213.4.23
TYPO3 CMS
TYPO3 Association
12.0.0 - 12.4.4012.4.41
TYPO3 CMS
TYPO3 Association
11.0.0 - 11.5.4811.5.49
TYPO3 CMS
TYPO3 Association
10.0.0 - 10.4.5410.4.55
AttributeDetail
CWECWE-862 (Missing Authorization)
Attack VectorNetwork (Authenticated)
CVSS v3.16.4 (Medium)
ImpactTraffic Hijacking, Phishing, SEO Poisoning
ConstraintRequires Backend User Account
Fix TypePatch (Logic Update)

MITRE ATT&CK Mapping

T1068Exploitation for Privilege Escalation
Privilege Escalation
T1566Phishing
Initial Access
T1078Valid Accounts
Defense Evasion
CWE-862
Missing Authorization

The software does not perform an authorization check when an actor attempts to access a resource or perform an action.

Known Exploits & Detection

Internal ResearchVulnerability disclosed by TYPO3 Security Team, logic flaw confirmed by patch analysis.

Vulnerability Timeline

Vendor Advisory Published
2026-01-13
CVE Published
2026-01-13
Patches Released
2026-01-13

References & Sources

  • [1]TYPO3-CORE-SA-2026-002 Advisory
  • [2]NVD Entry for CVE-2025-59021
  • [3]TYPO3 Source Code Repository

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•about 1 hour ago•CVE-2026-77331
2.0

CVE-2026-77331: Race Condition and Session State Corruption in memtomem-stm

CVE-2026-77331 (GHSA-72jh-722p-rqr3) is a concurrency and session-state synchronization vulnerability in memtomem-stm, a short-term memory proxy gateway for AI agents. In versions 0.1.2 prior to 0.1.34, concurrent Model Context Protocol (MCP) Remote Procedure Call (RPC) failures or mid-flight task cancellations can initiate duplicate reconnect loops and permit dirty or cancelled transport sessions to be reused. This deficiency results in session-state integrity loss and local service degradation.

Amit Schendel
Amit Schendel
1 views•9 min read
•about 2 hours ago•CVE-2026-132275
7.5

CVE-2026-132275: Exponential Resource Consumption via Nested <use> References in svglib

svglib versions prior to 2.3.1 contain an uncontrolled resource consumption vulnerability in the svg2rlg() renderer. When parsing SVG documents containing nested <use> elements, SvgRenderer.renderUse() recursively resolves and deep-copies referenced subtrees without enforcing a global expansion limit. Although the library detects and blocks direct circular references, an attacker can construct an acyclic directed reference graph with high fan-out (an SVG analogue to the XML Billion Laughs attack). Processing a crafted SVG payload of less than 2 KB triggers exponential node duplication, exhausting CPU and memory in applications that convert user-supplied SVGs or HTML documents embedding SVG content.

Amit Schendel
Amit Schendel
2 views•9 min read
•about 3 hours ago•CVE-2026-132277
5.3

CVE-2026-132277: Quadratic Memory Growth and Denial of Service in Inscriptis HTML-to-Text Library

CVE-2026-132277 (also tracked as GHSA-q87h-c5m7-659j) is an uncontrolled resource consumption and algorithmic complexity vulnerability in the Inscriptis Python library (versions 2.0.0 through 2.7.5). When rendering sibling HTML table elements inside a block-level parent container, the parser fails to pop the parent block's inline padding prefix from the internal canvas prefix stack upon closing the block. Consequently, each subsequent sibling table inherits and accumulates the indentation prefixes of all preceding tables. This causes the output string length and memory allocation of get_text() to grow quadratically with the number of sibling tables, allowing a compact untrusted HTML payload to trigger denial of service via memory exhaustion.

Amit Schendel
Amit Schendel
3 views•10 min read
•about 4 hours ago•CVE-2026-132276
5.9

CVE-2026-132276: Polynomial-Time Regular Expression Denial of Service (ReDoS) in wcmatch

CVE-2026-132276 (GHSA-53pm-wgxf-c6qf) is an algorithmic complexity and Regular Expression Denial of Service (ReDoS) vulnerability in the Python wcmatch wildcard and glob matching library prior to version 11.2. Under default flags, matching a non-matching attacker-controlled filename against a static developer-defined pattern containing multiple star (*) wildcards separated by literal delimiters causes polynomial-time backtracking O(n^k) in the compiled regular expression. A single 255-byte filename evaluated against a 5-star pattern consumes approximately 86 seconds of 100% CPU time, allowing unauthenticated attackers to induce severe availability degradation.

Alon Barad
Alon Barad
2 views•11 min read
•about 5 hours ago•CVE-2026-122244
7.7

CVE-2026-122244: Stored Cross-Site Scripting in Budibase Builder Formula Evaluation

CVE-2026-122244 (GHSA-r2q3-7m4h-63qg) is a high-severity cross-privilege Stored Cross-Site Scripting (XSS) vulnerability in Budibase prior to version 3.50.0. The flaw occurs due to defective character escaping in the JSON formatter utility combined with raw HTML rendering via Svelte's {@html} directive in the Budibase Builder interface. A low-privileged application user or an unauthenticated form visitor can store malicious HTML markup in a shared datasource, which subsequently executes arbitrary JavaScript in the browser session of an administrator or application builder inspecting Handlebars formula bindings.

Amit Schendel
Amit Schendel
4 views•9 min read
•about 6 hours ago•CVE-2026-122247
8.2

CVE-2026-122247: Unauthenticated Global-Admin and Database Creation via Tenant-Confusion Bypass in Budibase

A tenant-confusion vulnerability in the user initialization endpoint of the Budibase worker service (prior to version 3.50.0) allows unauthenticated remote attackers to bypass the one-time administrative setup guard. By supplying arbitrary tenant identifiers in POST requests to /api/global/users/init, an attacker can force the underlying CouchDB datastore to dynamically provision unlimited tenant databases and persist latent global administrator accounts. This results in datastore resource exhaustion, denial of service, and unauthorized administrative account creation inside non-default tenant contexts.

Amit Schendel
Amit Schendel
5 views•9 min read