How severe is CVE-2025-12998?

No CVSS score has been assigned to CVE-2025-12998 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-12998?

CVE-2025-12998 affects the following packages: codingms/modules (Packagist), codingms/modules (Packagist), codingms/modules (Packagist), codingms/modules (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2025-12998?

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

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for codingms/modules. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2025-12998 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-12998?

O3 pinpoints whether CVE-2025-12998 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

No public exploit code has been indexed for CVE-2025-12998 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.

What type of vulnerability is CVE-2025-12998?

CVE-2025-12998 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2025-12998 was published on November 12, 2025 and was last updated on July 15, 2026. 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

CVE-2025-12998

CVE-2025-12998 is a Improper Authentication vulnerability in codingms/modules. O3 Security confirms whether CVE-2025-12998 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Broken Authentication in extension “Modules” (modules)

Also known asGHSA-49qv-h8pm-73pf

Published

Nov 12, 2025

Updated

Jul 15, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Jul 15, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected

🐘codingms/modules🐘codingms/modules🐘codingms/modules🐘codingms/modules

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

Improper Authentication vulnerability in TYPO3 Extension "Modules" codingms/modules.This issue affects Extension "Modules": before 4.3.11, from 5.0.0 before 5.7.4, from 6.0.0 before 6.4.2, from 7.0.0 before 7.5.5.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`codingms/modules`	all versions	4.3.11
🐘Packagist	`codingms/modules`	≥ 5.0.0&&< 5.7.4	5.7.4
🐘Packagist	`codingms/modules`	≥ 7.0.0&&< 7.5.5	7.5.5
🐘Packagist	`codingms/modules`	≥ 6.0.0&&< 6.4.2	6.4.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for codingms/modules. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update codingms/modules to 4.3.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-12998 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 pinpoints whether CVE-2025-12998 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-12998. 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-12998 in your dependencies?

O3 detects CVE-2025-12998 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works