How severe is CVE-2010-3604?

No CVSS score has been assigned to CVE-2010-3604 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2010-3604?

CVE-2010-3604 affects the following packages: in2code/powermail (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2010-3604?

Update in2code/powermail to 1.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-3604 is resolved across your whole dependency graph.

How do I detect CVE-2010-3604 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for in2code/powermail, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2010-3604 actively exploited in the wild?

No public exploit code has been indexed for CVE-2010-3604 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-2010-3604?

CVE-2010-3604 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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-2010-3604?

CVE-2010-3604 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2010-3604 published, and has it been updated?

CVE-2010-3604 was published on May 17, 2022 and was last updated on April 12, 2025. 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-2010-3604 — powermail

CVE-2010-3604 is a SQL Injection vulnerability in in2code/powermail. A fix is available for in2code/powermail — see the affected versions and patch details below.

powermail extension for TYPO3 vulnerable to SQL Injection

Published

May 17, 2022

Updated

Apr 12, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘in2code/powermail

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

SQL injection vulnerability in the powermail extension 1.5.3 and earlier for TYPO3 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`in2code/powermail`	all versions	1.5.4`composer require in2code/powermail:^1.5.4`

Affected Products

1 product · 65 configurations

Application

powermailalex_kellner

≤ 1.5.2

64 versions

1.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.91.0.101.0.111.0.12

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for in2code/powermail, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update in2code/powermail to 1.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-3604 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

SQL injection vulnerability in the powermail extension 1.5.3 and earlier for TYPO3 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.

O3 Security · Impact-Aware SCA

Is CVE-2010-3604 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works