Email Subscriber Plugin up to 1.1 on WordPress AJAX Action kento_email_subscriber_ajax subscribe_email/subscribe_name cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Email Subscriber Plugin up to 1.1 on WordPress. The impacted element is the function kento_email_subscriber_ajax of the file /wp-admin/edit.php?post_type=kes_campaign&page=kento_email_subscriber_list_settings of the component AJAX Action Handler. Such manipulation of the argument subscribe_email/subscribe_name leads to cross site scripting.
This vulnerability is listed as CVE-2021-24556. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability, which was classified as problematic, has been found in Email Subscriber Plugin up to 1.1 on WordPress (WordPress Plugin). Affected by this issue is the function kento_email_subscriber_ajax of the file /wp-admin/edit.php?post_type=kes_campaign&page=kento_email_subscriber_list_settings of the component AJAX Action Handler. The manipulation of the argument subscribe_email/subscribe_name 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 weakness was presented 08/23/2021. The advisory is available at codevigilant.com. This vulnerability is handled as CVE-2021-24556. 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.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
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.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
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: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
01/14/2021 🔍08/23/2021 🔍
08/23/2021 🔍
08/26/2021 🔍
Sources
Advisory: codevigilant.comStatus: Not defined
CVE: CVE-2021-24556 (🔍)
GCVE (CVE): GCVE-0-2021-24556
GCVE (VulDB): GCVE-100-181298
Entry
Created: 08/23/2021 17:57Updated: 08/26/2021 06:47
Changes: 08/23/2021 17:57 (40), 08/26/2021 06:47 (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.