dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-7899

MEDIUM · 6.0 CVSS v4.0 Published 2025-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable 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
The powermail extension for TYPO3 allows Insecure Direct Object Reference resulting in download of arbitrary files from the webserver. This issue affects powermail version 12.0.0 up to 12.5.2 and version 13.0.0

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

The powermail TYPO3 extension contains an Insecure Direct Object Reference (IDOR) vulnerability that allows unauthorized users to download arbitrary files from the webserver by manipulating file path references in the application's download functionality.

MitigationUpdate powermail to version 12.5.3 or later (when available) which contains the patched version, or implement proper authorization validation in the file download handler to verify user permissions before allowing file access.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/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. Confirm powermail extension is installed
    Log into the TYPO3 backend and navigate to 'Admin Tools' > 'Extensions'. Look for 'powermail' in the list of installed extensions and verify its status shows as 'Loaded' or 'Active'.
    Affected if The powermail extension is installed and active in the TYPO3 instance
  2. Identify installed powermail version
    In the TYPO3 Extension Manager, click on the powermail extension to view its details. Note the version number displayed. Compare this against the affected version range (versions prior to the patched release).
    Affected if The installed version is within the affected range and has not been updated to the patched version
  3. Verify download functionality is accessible
    Examine the TYPO3 site for any forms or pages using powermail that include file download capabilities. Check the frontend for any download links or endpoints that reference file paths (often containing parameters like 'file', 'download', or 'path').
    Affected if The powermail download functionality is present and exposed on the website
  4. Test for IDOR vulnerability in download handler
    Attempt to access the download endpoint with a manipulated file path parameter pointing to a sensitive file outside the intended upload directory (for example, ../../../../etc/passwd or similar path traversal). Observe whether the server returns the file contents.
    Affected if The download endpoint returns files outside the intended directory, indicating the IDOR vulnerability is present

The environment is affected if powermail is installed, the version is unpatched, and the download functionality is accessible without proper authorization checks.

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 powermail to version 12.5.3 or later (when available) which contains the patched version, or implement proper authorization validation in the file download handler to verify user permissions before allowing file access.

Recommended fix Moderate confidence

Update to powermail version 12.5.3 or later (for the 12.x branch) or the next available version beyond 13.0.0 - verify exact version from TYPO3 security advisory

  1. 1. Check the official TYPO3 Security Advisory for powermail (CVE-2025-7899) on typo3.org or extensions.typo3.org to identify the exact fixed version
  2. 2. Backup your TYPO3 installation and database before performing any upgrade
  3. 3. Update the powermail extension to the fixed version using the TYPO3 Extension Manager or Composer
  4. 4. Clear all caches after the update via TYPO3 Install Tool or CLI: typo3cms cacheflush
  5. 5. Verify the fix by testing that the file download functionality no longer allows access to files outside the intended directory
Caveat Review release notes for any breaking changes between your current version and the target version; major version bumps (e.g., 12.x to 13.x) may include configuration or template changes

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7899 — 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-7899 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