| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in WordPress 2.0.11. It has been rated as problematic. The impacted element is an unknown function of the file wp-admin/options-discussion.php. This manipulation causes denial of service. Moreover, an exploit is present. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in WordPress 2.0.11 (Content Management System). Affected by this vulnerability is an unknown function of the file wp-admin/options-discussion.php. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability.
The bug was discovered 11/30/2013. The weakness was disclosed 12/17/2013 by MustLive as CSRF, DoS ?? IL ??????????? ? WordPress as confirmed advisory (Website). The advisory is shared at websecurity.com.ua. The public release happened without involvement of the project team. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
A public exploit has been developed by MustLive in HTTP Request and been published immediately after the advisory. It is possible to download the exploit at seclists.org. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 17 days. During that time the estimated underground price was around $5k-$25k. By approaching the search of inurl:wp-admin/options-discussion.php it is possible to find vulnerable targets with Google Hacking.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (90148) and OSVDB (101183†). The entry VDB-11558 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
Website
- Product: https://wordpress.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Highly functional
Author: MustLive
Programming Language: 🔍
Download: 🔍
Google Hack: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
11/30/2013 🔍12/17/2013 🔍
12/17/2013 🔍
12/20/2013 🔍
03/29/2019 🔍
Sources
Product: wordpress.comAdvisory: CSRF, DoS ?? IL ??????????? ? WordPress
Researcher: MustLive
Status: Confirmed
GCVE (VulDB): GCVE-100-11557
X-Force: 90148 - WordPress options-discussion.php denial of service, Medium Risk
OSVDB: 101183
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 12/20/2013 16:22Updated: 03/29/2019 16:56
Changes: 12/20/2013 16:22 (52), 03/29/2019 16:56 (5)
Complete: 🔍
Cache ID: 216:426:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.