Johntp adsense-deluxe 0.x on WordPress adsense-deluxe.php cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Johntp adsense-deluxe 0.x on WordPress. Affected is an unknown function of the file adsense-deluxe.php. The manipulation results in cross-site request forgery. This vulnerability was named CVE-2007-2828. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability, which was classified as problematic, was found in Johntp adsense-deluxe 0.x on WordPress (WordPress Plugin). Affected is some unknown functionality of the file adsense-deluxe.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 confidentiality, integrity, and availability. CVE summarizes:
Cross-site request forgery (CSRF) vulnerability in adsense-deluxe.php in the AdSense-Deluxe 0.x plugin for WordPress allows remote attackers to perform unspecified actions as arbitrary users via unspecified vectors.
The weakness was presented 05/20/2007 (Website). The advisory is shared for download at secunia.com. This vulnerability is traded as CVE-2007-2828 since 05/22/2007. It is possible to launch the attack remotely. A authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.
By approaching the search of inurl:adsense-deluxe.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 (34416), OSVDB (37291†) and Secunia (SA25335†). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.5
VulDB Temp Score: 4.9
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: 🔍
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: 🔍
Status: Unproven
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/20/2007 🔍05/22/2007 🔍
05/22/2007 🔍
05/22/2007 🔍
05/22/2007 🔍
03/13/2015 🔍
10/15/2017 🔍
Sources
Advisory: secunia.com⛔Status: Not defined
CVE: CVE-2007-2828 (🔍)
GCVE (CVE): GCVE-0-2007-2828
GCVE (VulDB): GCVE-100-36948
X-Force: 34416 - AdSense-Deluxe Wordpress plugin adsense-deluxe.php cross-site request forgery
Secunia: 25335 - WordPress AdSense-Deluxe Plugin Cross-Site Request Forgery, Less Critical
OSVDB: 37291 - AdSense-Deluxe Plugin for WordPress adsense-deluxe.php CSRF
Entry
Created: 03/13/2015 14:56Updated: 10/15/2017 11:30
Changes: 03/13/2015 14:56 (52), 10/15/2017 11:30 (6)
Complete: 🔍
Cache ID: 216:ED1:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.