Skip to main content
Mallory
UnratedVulnerability

CVE-2025-30081: Cross-site scripting in Clickstorm SEO extension for TYPO3

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-30081CWE-79

CVE-2025-30081 is a cross-site scripting (XSS) vulnerability in the Clickstorm SEO extension for TYPO3. According to the provided advisory, the flaw allows a logged-in TYPO3 backend user to inject improperly encoded input into HTML output rendered in the TYPO3 backend. The issue stems from insufficient output encoding of user-controlled input before it is included in backend HTML, enabling script-capable content to be executed in another user's browser within the backend context.

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 can result in execution of attacker-supplied JavaScript in the TYPO3 backend context. This may enable session compromise, theft of backend-accessible data, execution of unauthorized actions on behalf of the victim user, and other browser-based actions available through the victim's authenticated TYPO3 backend session.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, limit backend access to trusted users only, reduce the number of accounts with backend access, and monitor for suspicious or unexpected content entered through the extension that could be rendered in backend HTML. Because the issue requires a logged-in backend user to supply malicious input, restricting who can authenticate to the TYPO3 backend and reviewing extension-generated content can reduce exposure until the extension is upgraded.

Remediation

Patch, then assume compromise.

Upgrade the Clickstorm SEO extension to a fixed release. The provided advisory states that updates 6.7.0, 7.4.0, 8.3.0, and 9.2.0 are available for download, and for the listed affected package range, upgrading to version 9.2.0 or later remediates the issue.

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-30081 exploited in the wild?
As of Jun 13, 2026, Mallory has no reports of CVE-2025-30081 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-30081?
As of Jun 13, 2026, Mallory has found no public exploit for CVE-2025-30081.
Is there a patch for CVE-2025-30081?
Upgrade the Clickstorm SEO extension to a fixed release. The provided advisory states that updates 6.7.0, 7.4.0, 8.3.0, and 9.2.0 are available for download, and for the listed affected package range, upgrading to version 9.2.0 or later remediates the issue.
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.