WordPress component: A security weakness
WordPress component is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- WordPress component
- Plugin slug
Core- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Jan 10, 2008
This CVE was published Jan 10, 2008 and is one of 47 known issues for WordPress core.
Update, patch or deactivate.
No fixed release is identified. Update WordPress component when a confirmed fixed release becomes available; until then, disable and remove it when the site's risk warrants.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
WordPress 2.2.x and 2.3.x allows remote attackers to obtain sensitive information via an invalid p parameter in an rss2 action to the default URI, which reveals the full path and the SQL database structure.
NVD vector: AV:N/AC:L/Au:N/C:P/I:N/A:N
Primary and upstream sources
- NVD record for CVE-2008-0191
- Upstream reference lists.grok.org.uk
- Upstream reference securityreason.com
- Upstream reference securityvulns.ru
- Upstream reference websecurity.com.ua
- Upstream reference securityfocus.com
- Upstream reference exchange.xforce.ibmcloud.com
- Upstream reference lists.grok.org.uk
- Upstream reference securityreason.com
- Upstream reference securityvulns.ru
- Upstream reference websecurity.com.ua
- Upstream reference securityfocus.com
- Upstream reference exchange.xforce.ibmcloud.com