WP Smiley Plugin 1.4.1 on WordPress smilies4wp.php s4w-more cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in WP Smiley Plugin 1.4.1 on WordPress and classified as problematic. This affects an unknown function of the file smilies4wp.php. The manipulation of the argument s4w-more results in cross-site request forgery. This vulnerability is identified as CVE-2015-4140. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability classified as problematic has been found in WP Smiley Plugin 1.4.1 on WordPress (WordPress Plugin). Affected is an unknown code of the file smilies4wp.php. The manipulation of the argument s4w-more 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. CVE summarizes:
Cross-site request forgery (CSRF) vulnerability in the WP Smiley plugin 1.4.1 for WordPress allows remote attackers to hijack the authentication of editors for requests that conduct cross-site scripting (XSS) attacks via the s4w-more parameter to the smilies4wp.php page to wp-admin/options-general.php.
The weakness was released 06/18/2015 (Website). The advisory is shared for download at securityfocus.com. This vulnerability is traded as CVE-2015-4140 since 05/31/2015. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.
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†). Entry connected to this vulnerability is available at VDB-75995. Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
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: 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-4140 (🔍)
GCVE (CVE): GCVE-0-2015-4140
GCVE (VulDB): GCVE-100-75996
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:13
Changes: 06/19/2015 10:14 (50), 04/09/2019 16:13 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.