CVE-2025-53093 — starcitizentools/tabber-n…
HIGHFix: StarCitizenTools/mediawiki-extensions-TabberNeue@4cdf217CVE-2025-53093 is a high-severity (CVSS 8.6) Cross-site Scripting (XSS) vulnerability in starcitizentools/tabber-neue. A fix is available for starcitizentools/tabber-neue — see the affected versions and patch details below.
TabberNeue vulnerable to Stored XSS through wikitext
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-53093.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-53093 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
starcitizentools/tabber-neueReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Arbitrary HTML can be inserted into the DOM by inserting a payload into any allowed attribute of the <tabber> tag.
Details
The args provided within the wikitext as attributes to the <tabber> tag are passed to the TabberComponentTabs class:
https://github.com/StarCitizenTools/mediawiki-extensions-TabberNeue/blob/3a23b703ce36cfc4128e7921841f68230be4059a/includes/Tabber.php#L76
In TabberComponentTabs, the attributes are validated before being supplied to the Tabs template.
https://github.com/StarCitizenTools/mediawiki-extensions-TabberNeue/blob/3a23b703ce36cfc4128e7921841f68230be4059a/includes/Components/TabberComponentTabs.php#L15-L31
However, the validation is insufficient.
What Sanitizer::validateTagAttributes does is call validateAttributes, which
* - Discards attributes not on the given list
* - Unsafe style attributes are discarded
* - Invalid id attributes are re-encoded
However, the attribute values are expected to be escaped when inserted into HTML.
The attribute values are then inserted into HTML without being escaped: https://github.com/StarCitizenTools/mediawiki-extensions-TabberNeue/blob/3a23b703ce36cfc4128e7921841f68230be4059a/includes/templates/Tabs.mustache#L1
PoC
XSS through attributes:
- Go to Special:ExpandTemplates and insert the following wikitext:
<tabber class='test123" onmouseenter="alert(1)"'>
|-|First Tab Title=
First tab content goes here.
</tabber>
- Press "OK"
- Hover over the tabber
XSS through script tags:
- Go to Special:ExpandTemplates and insert the following wikitext:
<tabber class='test123"><script>alert(2)</script>'>
|-|First Tab Title=
First tab content goes here.
</tabber>
- Press "OK"
Impact
Arbitrary HTML can be inserted into the DOM by any user, allowing for JavaScript to be executed.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | starcitizentools/tabber-neue | ≥ 3.0.0&&< 3.1.1 | 3.1.1composer require starcitizentools/tabber-neue:^3.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for starcitizentools/tabber-neue, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update starcitizentools/tabber-neue to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-53093 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-53093 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-53093. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-53093 in your dependencies?
O3 Security finds CVE-2025-53093 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.