dbcve.org
PowermailTYPO3 extension · In2code

CVE-2024-45232

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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. It fails to validate the mail parameter of the confirmationAction, resulting in Insecure Direct Object Reference (IDOR). An unauthenticated attacker can use this to display the user-submitted data of all forms persisted by the extension. This can only be exploited when the extension is configured to save submitted form data to the database (plugin.tx_powermail.settings.db.enable=1), which however is the default setting of the extension. 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 an IDOR vulnerability in the confirmationAction where the mail parameter is not validated, allowing unauthenticated attackers to access any stored form submissions via direct object reference. Exploitation requires database storage to be enabled (plugin.tx_powermail.settings.db.enable=1), which is the default configuration.

MitigationUpdate to fixed versions 7.5.0, 8.5.0, 10.9.0, or 12.4.0, or disable database storage by setting plugin.tx_powermail.settings.db.enable=0.

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
Low
Integrity
None
Availability
None

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

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 powermail extension version
    Check the installed version by examining typo3conf/ext/powermail/ext_emconf.php or via TYPO3 extension manager. Compare the version number against the affected ranges: < 7.5.0, >= 8.0.0 and < 8.5.0, >= 9.0.0 and < 10.9.0, >= 12.0.0 and < 12.4.0
    Affected if The installed version falls within any of these vulnerable ranges
  2. Verify database storage is enabled
    Inspect TypoScript configuration (ts_template records) or LocalConfiguration.php for the setting plugin.tx_powermail.settings.db.enable. Also check the extension configuration in the TYPO3 backend under Admin Tools > Settings > Extension Configuration > powermail
    Affected if plugin.tx_powermail.settings.db.enable is set to 1, or is not explicitly set to 0 (the default behavior enables database storage)
  3. Test confirmationAction for unauthorized access
    Submit a test form via powermail and capture the confirmation URL. Then attempt to access the confirmationAction with a modified mail parameter (e.g., ?id=PAGEID&tx_powermail_pi1[action]=confirmation&tx_powermail_pi1[mail]=123 where 123 is a different submission ID). Observe if submission data from other records is returned
    Affected if The confirmationAction returns form submission data for mail IDs that were not created by the current request without requiring authentication

A system is affected if powermail is installed with a version in the vulnerable ranges AND database storage is enabled (the default setting), allowing the IDOR in confirmationAction to expose stored form submissions.

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

Update to fixed versions 7.5.0, 8.5.0, 10.9.0, or 12.4.0, or disable database storage by setting plugin.tx_powermail.settings.db.enable=0.

Recommended fix High confidence

Upgrade to Powermail 7.5.0 (for 7.x branch), 8.5.0 (for 8.x branch), 10.9.0 (for 9.x/10.x branch), or 12.4.0 (for 12.x branch) depending on your current version

  1. 1. Identify the currently installed Powermail version by checking composer.json or the TYPO3 extension manager
  2. 2. Determine which upgrade path applies: for Powermail 7.x upgrade to 7.5.0; for 8.x upgrade to 8.5.0; for 9.x or 10.x upgrade to 10.9.0; for 12.x upgrade to 12.4.0
  3. 3. Create a complete backup of the database and files
  4. 4. Update the extension via Composer: composer require/installer typoscript/powermail:"^7.5.0" (or the appropriate version for your branch)
  5. 5. Alternatively, update via TYPO3 extension manager in the backend
  6. 6. Clear all caches (flush caches in Install Tool or via CLI: vendor/bin/typo3 cache:flush)
  7. 7. Verify the extension version is correct in the extension manager
  8. 8. Test form submissions to confirm normal functionality
Caveat Check the release notes for your specific version jump for any breaking changes or deprecation notices

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

Fix this in Powermail Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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