WordPress WassUp plugin up to 1.7 wassup.php cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.67 |
Summary
A vulnerability, which was classified as problematic, was found in WordPress WassUp plugin up to 1.7. This affects an unknown part of the file wassup.php. Such manipulation leads to cross site scripting. This vulnerability is documented as CVE-2012-2633. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in WordPress WassUp plugin up to 1.7 (Content Management System). Affected by this issue is some unknown functionality of the file wassup.php. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. CVE summarizes:
Cross-site scripting (XSS) vulnerability in wassup.php in the WassUp plugin before 1.8.3.1 for WordPress allows remote attackers to inject arbitrary web script or HTML via the User-Agent HTTP header.
The weakness was released 06/15/2012 (Website). The advisory is available at wpwp.org. This vulnerability is handled as CVE-2012-2633 since 05/14/2012. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
By approaching the search of inurl:wassup.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.8 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (82017†). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://wordpress.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: WassUp plugin 1.8
Timeline
05/14/2012 🔍06/15/2012 🔍
06/15/2012 🔍
03/23/2015 🔍
01/16/2018 🔍
Sources
Vendor: wordpress.comAdvisory: wpwp.org
Status: Not defined
Confirmation: 🔍
CVE: CVE-2012-2633 (🔍)
GCVE (CVE): GCVE-0-2012-2633
GCVE (VulDB): GCVE-100-60986
OSVDB: 82017
Entry
Created: 03/23/2015 16:50Updated: 01/16/2018 08:22
Changes: 03/23/2015 16:50 (49), 01/16/2018 08:22 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.