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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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 is the EPSS score for CVE-2025-12998?

CVE-2025-12998 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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 October 28, 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 — modules

CVE-2025-12998 is a Improper Authentication vulnerability in codingms/modules. A fix is available for codingms/modules — see the affected versions and patch details below.

Broken Authentication in extension “Modules” (modules)

Also known asGHSA-49qv-h8pm-73pf

Published

Nov 12, 2025

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-12998.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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`composer require codingms/modules:^4.3.11`
🐘Packagist	`codingms/modules`	≥ 5.0.0&&< 5.7.4	5.7.4`composer require codingms/modules:^5.7.4`
🐘Packagist	`codingms/modules`	≥ 7.0.0&&< 7.5.5	7.5.5`composer require codingms/modules:^7.5.5`
🐘Packagist	`codingms/modules`	≥ 6.0.0&&< 6.4.2	6.4.2`composer require codingms/modules:^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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-12998 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works