HCL Aftermarket DPC 1.0.0 unmaintained third party components
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in HCL Aftermarket DPC 1.0.0. It has been classified as problematic. This affects an unknown function. The manipulation leads to use of unmaintained third party components. This vulnerability is listed as CVE-2025-55277. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as problematic, has been found in HCL Aftermarket DPC 1.0.0. This issue affects an unknown code block. The manipulation with an unknown input leads to a use of unmaintained third party components vulnerability. Using CWE to declare the problem leads to CWE-1104. The product relies on third-party components that are not
actively supported or maintained by the original developer or a trusted proxy
for the original developer. Impacted is confidentiality. The summary by CVE is:
HCL Aftermarket DPC is affected by Use of Vulnerable/Outdated Versions vulnerability using which an attacker may make use of the exploits available across the internet and craft attacks against the application.
It is possible to read the advisory at support.hcl-software.com. The identification of this vulnerability is CVE-2025-55277 since 08/12/2025. The exploitation is known to be difficult. The attack may be initiated remotely. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.9VulDB Meta Temp Score: 2.9
VulDB Base Score: 3.1
VulDB Temp Score: 3.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 2.6
CNA Vector (HCL): 🔒
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: Use of unmaintained third party componentsCWE: CWE-1104
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
08/12/2025 CVE reserved03/26/2026 Advisory disclosed
03/26/2026 VulDB entry created
03/26/2026 VulDB entry last update
Sources
Advisory: KB0129793Status: Confirmed
CVE: CVE-2025-55277 (🔒)
GCVE (CVE): GCVE-0-2025-55277
GCVE (VulDB): GCVE-100-353603
Entry
Created: 03/26/2026 14:51Updated: 03/26/2026 14:55
Changes: 03/26/2026 14:51 (60), 03/26/2026 14:55 (1)
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.