CVE-2011-3122
First published: Wed Aug 10 2011(Updated: )
Unspecified vulnerability in WordPress 3.1 before 3.1.3 and 3.2 before Beta 2 has unknown impact and attack vectors related to "Media security."
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress | =3.1 | |
| WordPress | =3.1.1 | |
| WordPress | =3.1.2 | |
| WordPress | =3.2-beta1 |
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-3122?
The severity of CVE-2011-3122 is currently unspecified, which means its impact and potential attack vectors are not fully understood.
How do I fix CVE-2011-3122?
To fix CVE-2011-3122, update your WordPress installation to version 3.1.3 or later.
Which versions of WordPress are affected by CVE-2011-3122?
CVE-2011-3122 affects WordPress versions 3.1, 3.1.1, 3.1.2, and the beta 1 of version 3.2.
What type of vulnerability is CVE-2011-3122?
CVE-2011-3122 is described as an unspecified vulnerability related to media security.
Can CVE-2011-3122 be exploited remotely?
The specific attack vectors for CVE-2011-3122 are mentioned as unknown, leaving uncertainty about its exploitability.
- agent/type
- agent/softwarecombine
- agent/remedy
- agent/references
- 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-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/wordpress
- canonical/wordpress
- version/wordpress/3.1
- version/wordpress/3.1.1
- version/wordpress/3.1.2
- version/wordpress/3.2-beta1