CVE-2006-6016
First published: Tue Nov 21 2006(Updated: )
wp-admin/user-edit.php in WordPress before 2.0.5 allows remote authenticated users to read the metadata of an arbitrary user via a modified user_id parameter.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress | <=2.0.4 | |
| <=2.0.4 |
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-2006-6016?
CVE-2006-6016 has been assigned a medium severity rating due to the potential for unauthorized metadata access.
How do I fix CVE-2006-6016?
To fix CVE-2006-6016, upgrade your WordPress installation to version 2.0.5 or later.
Who is affected by CVE-2006-6016?
CVE-2006-6016 affects remote authenticated users of WordPress versions prior to 2.0.5.
What is the impact of CVE-2006-6016?
The impact of CVE-2006-6016 allows attackers to read sensitive metadata from arbitrary user accounts.
Is there a workaround for CVE-2006-6016?
There is no specific workaround for CVE-2006-6016; the best practice is to update to the secure version of WordPress.
- agent/type
- agent/remedy
- agent/references
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- collector/nvd-historical
- vendor/wordpress
- product/wordpress
- canonical/wordpress wordpress
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/source
- agent/last-modified-date
- agent/weakness
- agent/tags
- collector/nvd-api
- source/NVD
- canonical/wordpress
- version/wordpress/2.0.4