| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Alcatel Lucent OmniAccess Stellar. This affects an unknown part. This manipulation causes cross site scripting. The identification of this vulnerability is CVE-2025-52687. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability classified as problematic was found in Alcatel Lucent OmniAccess Stellar (affected version not known). Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. The summary by CVE is:
Successful exploitation of the vulnerability could allow an attacker with administrator credentials for the access point to inject malicious JavaScript into the payload of web traffics, potentially leading to session hijacking and denial-of-service (DoS).
The weakness was shared by Jay Turla, Japz Divino and Jerold Camacho. The advisory is shared at csa.gov.sg. This vulnerability is known as CVE-2025-52687 since 06/19/2025. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are needed for exploitation. 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.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21577). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.4VulDB Meta Temp Score: 2.4
VulDB Base Score: 2.4
VulDB Temp Score: 2.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 2.4
CNA Vector (CSA): 🔒
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
06/19/2025 CVE reserved07/16/2025 Advisory disclosed
07/16/2025 VulDB entry created
07/16/2025 VulDB entry last update
Sources
Advisory: csa.gov.sgResearcher: Jay Turla, Japz Divino, Jerold Camacho
Status: Confirmed
CVE: CVE-2025-52687 (🔒)
GCVE (CVE): GCVE-0-2025-52687
GCVE (VulDB): GCVE-100-316549
EUVD: 🔒
Entry
Created: 07/16/2025 09:38Updated: 07/16/2025 15:49
Changes: 07/16/2025 09:38 (61), 07/16/2025 10:27 (1), 07/16/2025 15:49 (1)
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.