How severe is CVE-2025-30083?

CVE-2025-30083 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-30083?

CVE-2025-30083 affects the following packages: codingms/additional-tca (Packagist), codingms/additional-tca (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2025-30083?

Update codingms/additional-tca to 1.16.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-30083 is resolved across your whole dependency graph.

How do I detect CVE-2025-30083 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for codingms/additional-tca, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-30083 if there is no patch (or I can't update yet)?

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 does O3 Security protect against CVE-2025-30083?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-30083 can be triaged on real exposure rather than presence alone.

Is CVE-2025-30083 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-30083 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2025-30083 published, and has it been updated?

CVE-2025-30083 was published on March 19, 2025 and was last updated on March 19, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2025-30083 — codingms/additional-tca

MEDIUM

CVE-2025-30083 is a medium-severity (CVSS 5.5) vulnerability in codingms/additional-tca. A fix is available for codingms/additional-tca — see the affected versions and patch details below.

Additional TCA Allows Cross-Site Scripting (XSS)

Published

Mar 19, 2025

Updated

Mar 19, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Mar 19, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘codingms/additional-tca🐘codingms/additional-tca

Real-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

A cross-site scripting (XSS) vulnerability has been discovered in the Additional TCA extension. This vulnerabily is exploitable by a logged in backend user utilizing the TYPO3 backend user interface. This user can create output in the HTML context by exploiting improperly encoded user input. Updates 1.15.17 and 1.16.9 are available for download.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`codingms/additional-tca`	≥ 1.16.0&&< 1.16.9	1.16.9`composer require codingms/additional-tca:^1.16.9`
🐘Packagist	`codingms/additional-tca`	≥ 1.7.0&&< 1.15.17	1.15.17`composer require codingms/additional-tca:^1.15.17`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for codingms/additional-tca, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update codingms/additional-tca to 1.16.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-30083 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-30083 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-30083. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-30083 in your dependencies?

O3 Security finds CVE-2025-30083 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works