WP Cleanfix Plugin 2.4.4 on WordPress wpCleanFixAjax.php cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in WP Cleanfix Plugin 2.4.4 on WordPress and classified as problematic. This affects an unknown function of the file wpCleanFixAjax.php. Performing a manipulation results in cross-site request forgery. This vulnerability is identified as CVE-2013-2108. The attack can be initiated remotely. Additionally, an exploit exists.
Details
A vulnerability, which was classified as problematic, was found in WP Cleanfix Plugin 2.4.4 on WordPress. This affects an unknown part of the file wpCleanFixAjax.php. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity.
It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2013-2108 since 02/19/2013. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details and a public exploit are known.
The exploit is shared for download at openwall.com. It is declared as proof-of-concept. By approaching the search of inurl:wpCleanFixAjax.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (84435), Exploit-DB (38520) and SecurityFocus (BID 59940†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/19/2013 🔍03/24/2025 🔍
03/24/2025 🔍
04/03/2025 🔍
Sources
Advisory: 59940⛔Status: Not defined
CVE: CVE-2013-2108 (🔍)
GCVE (CVE): GCVE-0-2013-2108
GCVE (VulDB): GCVE-100-300891
X-Force: 84435
SecurityFocus: 59940
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/24/2025 20:51Updated: 04/03/2025 03:44
Changes: 03/24/2025 20:51 (75), 04/03/2025 03:44 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.