CVE-2011-3129
First published: Wed Aug 10 2011(Updated: )
The file upload functionality in WordPress 3.1 before 3.1.3 and 3.2 before Beta 2, when running "on hosts with dangerous security settings," has unknown impact and attack vectors, possibly related to dangerous filenames.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress | =3.1 | |
| WordPress | =3.2-beta1 | |
| WordPress | =3.1.2 | |
| WordPress | =3.1.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2011-3129?
The severity of CVE-2011-3129 is considered moderate due to potential impacts from dangerous file uploads.
How do I fix CVE-2011-3129?
To fix CVE-2011-3129, upgrade to WordPress version 3.1.3 or later.
Which versions of WordPress are affected by CVE-2011-3129?
CVE-2011-3129 affects WordPress versions 3.1 prior to 3.1.3 and 3.2 before Beta 2.
Can CVE-2011-3129 be exploited remotely?
Yes, CVE-2011-3129 can potentially be exploited remotely on hosts with misconfigured security settings.
What specific functionality does CVE-2011-3129 affect in WordPress?
CVE-2011-3129 affects the file upload functionality in WordPress.
- agent/references
- agent/type
- agent/softwarecombine
- agent/remedy
- agent/weakness
- agent/author
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/wordpress
- canonical/wordpress
- version/wordpress/3.1
- version/wordpress/3.2-beta1
- version/wordpress/3.1.2
- version/wordpress/3.1.1