CVE-2025-4130 json
Hardcoded Credentials in PAVO Inc.'s PAVO Pay
published last yr. modified 4mo ago also EUVD-2025-22094
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Use of Hard-coded Credentials vulnerability in PAVO Inc. PAVO Pay allows Read Sensitive Constants Within an Executable.
This issue affects PAVO Pay: before 13.05.2025.
Patch / fix
- PAVO Inc. PAVO Pay 13.05.2025
Is CVE-2025-4130 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- PAVO Inc. PAVO Pay
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
usom.gov.tr
/bildirim/tr-25-0166
government-resource, broken-link
-
siberguvenlik.gov.tr
/guvenlik-bildirimleri/detay/tr-25-0166
government-resource
Sources
- CVE List CVE-2025-4130
- NVD CVE-2025-4130
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.