dbcve.org
PowermailTYPO3 extension · In2code

CVE-2024-45233

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to 7.5.0 / 8.5.0 or later.
See remediation →
100/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
An issue was discovered in powermail extension through 12.3.5 for TYPO3. Several actions in the OutputController can directly be called, due to missing or insufficiently implemented access checks, resulting in Broken Access Control. Depending on the configuration of the Powermail Frontend plugins, an unauthenticated attacker can exploit this to edit, update, delete, or export data of persisted forms. This can only be exploited when the Powermail Frontend plugins are used. The fixed versions are 7.5.0, 8.5.0, 10.9.0, and 12.4.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 · high confidence

The powermail TYPO3 extension has a Broken Access Control vulnerability in the OutputController where several actions lack proper authorization checks. An unauthenticated attacker can directly invoke these actions to edit, update, delete, or export data from persisted forms when Powermail Frontend plugins are enabled.

MitigationImmediately update the powermail extension to one of the fixed versions (7.5.0, 8.5.0, 10.9.0, or 12.4.0) matching the TYPO3 version in use, as this is a critical unauthenticated data manipulation vulnerability.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PowermailTYPO3 extension
Affected:< 7.5.0>= 8.0.0, < 8.5.0>= 9.0.0, < 10.9.0>= 12.0.0, < 12.4.0

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 powermail extension version
    Check the powermail extension version in TYPO3 extension manager, or run 'composer show in2code/powermail' if installed via Composer, or inspect the ext_emconf.php file in the powermail extension directory
    Affected if The installed version is < 7.5.0 OR >= 8.0.0 and < 8.5.0 OR >= 9.0.0 and < 10.9.0 OR >= 12.0.0 and < 12.4.0
  2. Confirm powermail frontend plugin is active
    In TYPO3 backend, go to Plugins module and verify that any powermail frontend plugin (such as Powermail Form or Powermail Static) is enabled and assigned to at least one page, or check tt_content records for CType 'powermail'
    Affected if A powermail frontend plugin is active on the website (this is required for the vulnerability to be exploitable)
  3. Check OutputController action accessibility
    Inspect the OutputController class in the powermail extension (typically at Classes/Controller/OutputController.php) and verify if the affected actions (edit, update, delete, export) lack @TYPO3\CMS\Extbase\Mvc\Controller\ActionController or @validate annotations, or check for missing TYPO3\CMS\Extbase\Annotation\IgnoreValidation on action methods
    Affected if The OutputController actions are accessible without authorization checks (only verifiable by reviewing the source code directly)
  4. Confirm vulnerability exposure
    Attempt a direct request to a powermail output action URL pattern such as /?id=PAGEID&tx_powermail_pi1[action]=edit&tx_powermail_pi1[controller]=Output (without prior authentication) to test if unauthorized access is possible
    Affected if Unauthenticated users can access edit, update, delete, or export actions in the OutputController

You are affected if the powermail extension version falls within any of the vulnerable ranges AND a frontend plugin is enabled, allowing unauthenticated access to data manipulation actions.

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
Upgrade available Upgrade to 7.5.0 / 8.5.0 / 10.9.0 or later
Fixed in 7.5.08.5.010.9.0
Interim mitigation

Immediately update the powermail extension to one of the fixed versions (7.5.0, 8.5.0, 10.9.0, or 12.4.0) matching the TYPO3 version in use, as this is a critical unauthenticated data manipulation vulnerability.

Recommended fix High confidence

Upgrade to Powermail 7.5.0, 8.5.0, 10.9.0, or 12.4.0 depending on your current major version branch

  1. 1. Identify the current installed version of the Powermail extension in your TYPO3 instance
  2. 2. Based on your current major version, upgrade to the corresponding fixed version: 7.x -> 7.5.0, 8.x -> 8.5.0, 9.x/10.x -> 10.9.0, 12.x -> 12.4.0
  3. 3. Use the TYPO3 extension manager (Extension Manager) or Composer to update the Powermail extension to the fixed version
  4. 4. Clear all caches after the upgrade (Install Tool > Clear Cache or 'composer dump-autoload' if using Composer)
  5. 5. Verify that Powermail Frontend plugins continue to function correctly
  6. 6. Test that the access control issue is resolved by confirming that unauthenticated users can no longer access OutputController actions directly
Caveat Review the change logs between your current version and the target fixed version for any breaking changes, particularly when upgrading across major version branches

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

Fix this in Powermail Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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