Strategic Overview
- Status
- Patched in 2.8.5
- Affected Core
- WordPress 2.8
- Affected Version
<= 2.8.4- CVSS
- 6.5Medium
- Weakness type
- CWE-400 · Uncontrolled Resource Consumption
- CVE
CVE-2009-3622
At a glance
CVE-2009-3622 is a medium-severity Uncontrolled Resource Consumption vulnerability in the WordPress 2.8 WordPress release line, affecting <= 2.8.4. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high availability impact). The issue is fixed in version 2.8.5; sites on affected versions should update now. Disclosed October 2009.
Vulnerability Overview
Algorithmic complexity vulnerability in wp-trackback.php in WordPress before 2.8.5 allows remote attackers to cause a denial of service (CPU consumption and server hang) via a long title parameter in conjunction with a charset parameter composed of many comma-separated "UTF-8" substrings, related to the mb_convert_encoding function in PHP.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on availability.
CWE-400: Uncontrolled Resource Consumption
WordPress 2.8 <= 2.8.4 carries this weakness at UTF-8, and reaching it takes a caller who can reach the endpoint. Uncontrolled resource consumption means a request can make the server do an amount of work it never bounds, because the size or repetition of the job is taken from the request rather than capped by the code.
A single caller can hold PHP workers, database connections or disk open long enough to slow the site for everyone, without needing any account or any other flaw. For WordPress 2.8 the fix is 2.8.5: builds <= 2.8.4 are affected, anything from 2.8.5 onward is not.
Remediation
Update to version 2.8.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WordPress 2.8: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: updating to 2.8.5 is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WordPress 2.8
- 9.8CVE-2026-63030: WordPress Core 6.9 - 7.0.1 Remote Code Execution
CVE-2026-63030 - 9.8CVE-2024-31211: WordPress Core 6.4.0 - 6.4.1 RCE POP Chain
CVE-2024-31211 - 9.8WordPress Core < 6.0.3 SQL Injection via WP_Date_Query
- 9.8CVE-2021-29476: WordPress Core < 5.5.3 PHP Object Injection Gadget
CVE-2021-29476 - 9.8CVE-2017-16510: WordPress Core SQL Injection
CVE-2017-16510 - 9.8CVE-2017-14723: WordPress Core < 4.8.2 SQL Injection
CVE-2017-14723 - 9.8CVE-2007-6013: WordPress Core 1.5 - 2.3.1 Authorization Bypass
CVE-2007-6013 - 9.8CVE-2007-6318: WordPress Core < 2.3.2 SQL Injection
CVE-2007-6318
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C