WP Smiley Plugin 1.4.1 on WordPress smilies4wp.php s4w-more cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in WP Smiley Plugin 1.4.1 on WordPress and classified as problematic. The impacted element is an unknown function of the file smilies4wp.php. The manipulation of the argument s4w-more leads to cross site scripting. This vulnerability is referenced as CVE-2015-4139. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in WP Smiley Plugin 1.4.1 on WordPress (WordPress Plugin). It has been rated as problematic. This issue affects an unknown part of the file smilies4wp.php. The manipulation of the argument s4w-more 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. The summary by CVE is:
Cross-site scripting (XSS) vulnerability in smilies4wp.php in the WP Smiley plugin 1.4.1 for WordPress allows remote authenticated users to inject arbitrary web script or HTML via the s4w-more parameter to wp-admin/options-general.php.
The weakness was published 06/18/2015 (Website). It is possible to read the advisory at securityfocus.com. The identification of this vulnerability is CVE-2015-4139 since 05/31/2015. The exploitation is known to be easy. The attack may be initiated remotely. A simple authentication is necessary for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
By approaching the search of inurl:smilies4wp.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 vulnerability database at SecurityFocus (BID 74914†). Similar entry is available at VDB-75996. 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: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/29/2015 🔍05/31/2015 🔍
06/18/2015 🔍
06/18/2015 🔍
06/19/2015 🔍
04/09/2019 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2015-4139 (🔍)
GCVE (CVE): GCVE-0-2015-4139
GCVE (VulDB): GCVE-100-75995
SecurityFocus: 74914 - WordPress wp-smiley Plugin HTML Injection and Cross Site Request Forgery Vulnerabilities
See also: 🔍
Entry
Created: 06/19/2015 10:14Updated: 04/09/2019 16:10
Changes: 06/19/2015 10:14 (50), 04/09/2019 16:10 (3)
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.