Skip to main content
Mallory
UnratedVulnerability

CVE-2025-30083: XSS in TYPO3 Additional TCA extension

Updated 5 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2025-30083CWE-79

CVE-2025-30083 is a cross-site scripting vulnerability in the codingms/additional-tca extension for TYPO3. According to the provided advisory, improperly encoded user input can be used by an authenticated TYPO3 backend user to create malicious output in an HTML context within the TYPO3 backend. The issue is therefore an authenticated backend-context XSS caused by insufficient output encoding of user-controlled data.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a logged-in TYPO3 backend user to inject and execute arbitrary script in the TYPO3 backend context. This can lead to theft or misuse of backend session data, execution of unauthorized actions with the victim user's privileges, and manipulation of backend content or administrative workflows.

Remediation

Patch, then assume compromise.

Upgrade the Packagist package codingms/additional-tca to a fixed release. Based on the provided advisory, fixed versions include 1.15.17 and 1.16.9; for affected 1.16.x deployments, update to 1.16.9 or later. Apply the vendor-provided patched version appropriate to the deployed branch.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-30083 exploited in the wild?
As of Jun 12, 2026, Mallory has no reports of CVE-2025-30083 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-30083?
As of Jun 12, 2026, Mallory has found no public exploit for CVE-2025-30083.
Is there a patch for CVE-2025-30083?
Upgrade the Packagist package codingms/additional-tca to a fixed release. Based on the provided advisory, fixed versions include 1.15.17 and 1.16.9; for affected 1.16.x deployments, update to 1.16.9 or later.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.