Social Sharing Plugin up to 3.3.62 on WordPress Setting cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Social Sharing Plugin up to 3.3.62 on WordPress and classified as problematic. The affected element is an unknown function of the component Setting Handler. Performing a manipulation results in cross site scripting. This vulnerability is identified as CVE-2024-4924. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in Social Sharing Plugin up to 3.3.62 on WordPress. This affects an unknown part of the component Setting Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as 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. This is going to have an impact on integrity. The summary by CVE is:
The Social Sharing Plugin WordPress plugin before 3.3.63 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)
The weakness was released by Dmitrii Ignatyev. It is possible to read the advisory at wpscan.com. This vulnerability is uniquely identified as CVE-2024-4924 since 05/15/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. The exploitation needs additional levels of successful authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
Upgrading to version 3.3.63 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
- 3.3.0
- 3.3.1
- 3.3.2
- 3.3.3
- 3.3.4
- 3.3.5
- 3.3.6
- 3.3.7
- 3.3.8
- 3.3.9
- 3.3.10
- 3.3.11
- 3.3.12
- 3.3.13
- 3.3.14
- 3.3.15
- 3.3.16
- 3.3.17
- 3.3.18
- 3.3.19
- 3.3.20
- 3.3.21
- 3.3.22
- 3.3.23
- 3.3.24
- 3.3.25
- 3.3.26
- 3.3.27
- 3.3.28
- 3.3.29
- 3.3.30
- 3.3.31
- 3.3.32
- 3.3.33
- 3.3.34
- 3.3.35
- 3.3.36
- 3.3.37
- 3.3.38
- 3.3.39
- 3.3.40
- 3.3.41
- 3.3.42
- 3.3.43
- 3.3.44
- 3.3.45
- 3.3.46
- 3.3.47
- 3.3.48
- 3.3.49
- 3.3.50
- 3.3.51
- 3.3.52
- 3.3.53
- 3.3.54
- 3.3.55
- 3.3.56
- 3.3.57
- 3.3.58
- 3.3.59
- 3.3.60
- 3.3.61
- 3.3.62
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.2
VulDB Base Score: 2.4
VulDB Temp Score: 2.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.1
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 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Social Sharing Plugin 3.3.63
Timeline
05/15/2024 🔍06/12/2024 🔍
06/12/2024 🔍
03/24/2025 🔍
Sources
Advisory: wpscan.comResearcher: Dmitrii Ignatyev
Status: Confirmed
CVE: CVE-2024-4924 (🔍)
GCVE (CVE): GCVE-0-2024-4924
GCVE (VulDB): GCVE-100-268131
Entry
Created: 06/12/2024 08:12Updated: 03/24/2025 04:06
Changes: 06/12/2024 08:12 (56), 06/14/2024 14:02 (1), 10/29/2024 04:46 (12), 03/24/2025 04:06 (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.