Shahjada Download Manager Plugin up to 3.3.53 on WordPress cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Shahjada Download Manager Plugin up to 3.3.53 on WordPress. It has been rated as problematic. Affected by this issue is some unknown functionality. Performing a manipulation results in cross site scripting. This vulnerability is identified as CVE-2026-39615. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in Shahjada Download Manager Plugin up to 3.3.53 on WordPress. It has been classified as problematic. This affects an unknown function. 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:
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Shahjada Download Manager download-manager allows Stored XSS.This issue affects Download Manager: from n/a through <= 3.3.53.
The weakness was released by Hhhai. The advisory is shared at patchstack.com. This vulnerability is uniquely identified as CVE-2026-39615 since 04/07/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
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
Vendor
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
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
04/07/2026 CVE reserved04/08/2026 Advisory disclosed
04/08/2026 VulDB entry created
04/08/2026 VulDB entry last update
Sources
Advisory: patchstack.comResearcher: Hhhai
Status: Not defined
CVE: CVE-2026-39615 (🔒)
GCVE (CVE): GCVE-0-2026-39615
GCVE (VulDB): GCVE-100-356181
Entry
Created: 04/08/2026 12:49Changes: 04/08/2026 12:49 (55)
Complete: 🔍
Cache ID: 216:DEF: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.