dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-12998

HIGH · 8.2 CVSS v4.0 Published 2025-11-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Improper Authentication vulnerability in the TYPO3 extension 'Modules' (codingms/modules) allows attackers to bypass authentication mechanisms. The vulnerability affects multiple version ranges before the patched releases (4.3.11, 5.7.4, 6.4.2, 7.5.5), potentially granting unauthorized access to protected resources.

MitigationUpdate the Modules extension to the patched versions (4.3.11, 5.7.4, 6.4.2, or 7.5.5 depending on your current major version) to remediate the authentication bypass.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Modules extension version
    Check the extension version via TYPO3 Extension Manager (Admin Tools > Extensions > Modules) or inspect composer.json / ext_emconf.php in typo3conf/ext/modules/ or vendor/codingms/modules/
    Affected if The extension version is below 4.3.11, 5.7.4, 6.4.2, or 7.5.5 depending on your major version branch
  2. Confirm extension is active
    Verify the Modules extension is loaded and enabled in your TYPO3 installation through the Extension Manager or Configuration/ActiveExtensions.php
    Affected if The extension is installed and active in your TYPO3 instance
  3. Check for protected module usage
    Review your TYPO3 backend for any protected modules or actions provided by the codingms/modules extension that should require authentication
    Affected if The extension provides authenticated backend modules or frontend routes that are exposed without proper authentication

Your environment is affected if the codingms/modules extension is installed and active with a version lower than the patched releases (4.3.11, 5.7.4, 6.4.2, or 7.5.5), allowing potential unauthorized access to protected resources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Modules extension to the patched versions (4.3.11, 5.7.4, 6.4.2, or 7.5.5 depending on your current major version) to remediate the authentication bypass.

Recommended fix High confidence

Upgrade to extension version 7.5.5 (or the latest in your current major branch: 4.3.11, 5.7.4, or 6.4.2)

  1. Log in to the TYPO3 backend as an administrator with extension management permissions
  2. Navigate to the Extension Manager (ADMIN TOOLS > Extensions)
  3. Locate the 'modules' extension (codingms/modules) in the list of installed extensions
  4. Check the current installed version to determine which upgrade path applies
  5. Click on the extension and select 'Update' to install the latest compatible version: 7.5.5 for version 7.x, 6.4.2 for version 6.x, 5.7.4 for version 5.x, or 4.3.11 for version 4.x
  6. After update, clear the TYPO3 cache (Maintenance > Flush caches)
  7. Verify the extension is now running the patched version
  8. Test that the Modules extension functionality works correctly post-update
Caveat Minor version security patches typically have no breaking changes; however, always review extension release notes before upgrading in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12998 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12998 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data