wp-code-highlightjs Plugin up to 0.6.2 on WordPress options-general.php?page=wp-code-highlight-js hljs_additional_css cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in wp-code-highlightjs Plugin up to 0.6.2 on WordPress. It has been classified as problematic. Affected by this issue is some unknown functionality of the file wp-admin/options-general.php?page=wp-code-highlight-js. Performing a manipulation of the argument hljs_additional_css results in cross-site request forgery. This vulnerability is identified as CVE-2019-12934. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in wp-code-highlightjs Plugin up to 0.6.2 on WordPress (WordPress Plugin). It has been classified as problematic. This affects an unknown code block of the file wp-admin/options-general.php?page=wp-code-highlight-js. The manipulation of the argument hljs_additional_css 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. The summary by CVE is:
An issue was discovered in the wp-code-highlightjs plugin through 0.6.2 for WordPress. wp-admin/options-general.php?page=wp-code-highlight-js allows CSRF, as demonstrated by an XSS payload in the hljs_additional_css parameter.
The weakness was released 07/20/2019 (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2019-12934 since 06/23/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
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 the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
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
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
06/23/2019 🔍07/20/2019 🔍
07/20/2019 🔍
11/05/2023 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2019-12934 (🔍)
GCVE (CVE): GCVE-0-2019-12934
GCVE (VulDB): GCVE-100-138381
SecurityFocus: 109331
Entry
Created: 07/20/2019 09:14Updated: 11/05/2023 09:02
Changes: 07/20/2019 09:14 (56), 07/08/2020 22:24 (1), 11/05/2023 09:02 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.