HL Twitter Plugin up to 2014.1.18 on WordPress Setting cross-site request forgery
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
3.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in HL Twitter Plugin up to 2014.1.18 on WordPress. Affected by this issue is some unknown functionality of the component Setting Handler. The manipulation leads to cross-site request forgery. This vulnerability is handled as CVE-2024-3629. The attack may be launched remotely. There is no exploit available. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability classified as problematic was found in HL Twitter Plugin up to 2014.1.18 on WordPress. Affected by this vulnerability is an unknown part of the component Setting Handler. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. The summary by CVE is:
The HL Twitter WordPress plugin through 2014.1.18 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack
The weakness was released by Bob Matyas. The advisory is shared at wpscan.com. This vulnerability is known as CVE-2024-3629 since 04/10/2024. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 2014.1.0
- 2014.1.1
- 2014.1.2
- 2014.1.3
- 2014.1.4
- 2014.1.5
- 2014.1.6
- 2014.1.7
- 2014.1.8
- 2014.1.9
- 2014.1.10
- 2014.1.11
- 2014.1.12
- 2014.1.13
- 2014.1.14
- 2014.1.15
- 2014.1.16
- 2014.1.17
- 2014.1.18
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.4VulDB Meta Temp Score: 3.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 2.4
CNA 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: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
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
04/10/2024 🔍05/15/2024 🔍
05/15/2024 🔍
03/30/2025 🔍
Sources
Advisory: wpscan.comResearcher: Bob Matyas
Status: Not defined
CVE: CVE-2024-3629 (🔍)
GCVE (CVE): GCVE-0-2024-3629
GCVE (VulDB): GCVE-100-264421
Entry
Created: 05/15/2024 09:48 AMUpdated: 03/30/2025 03:48 AM
Changes: 05/15/2024 09:48 AM (54), 11/20/2024 08:54 PM (13), 03/30/2025 03:48 AM (3)
Complete: 🔍
Cache ID: 18:8B3:40
No comments yet. Languages: en.
Please log in to comment.