CVE-2014-125030 json
taoeffect Empress hard-coded password
published 3y ago modified 4mo ago also EUVD-2014-1202
- cvss
- 6.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
A vulnerability, which was classified as critical, has been found in taoeffect Empress. Affected by this issue is some unknown functionality. The manipulation leads to use of hard-coded password. The patch is identified as 557e177d8a309d6f0f26de46efb38d43e000852d. It is recommended to apply a patch to fix this issue. VDB-217154 is the identifier assigned to this vulnerability.
Patch / fix
- empress_project empress 2014-12-02
- github.com/taoeffect/empress@557e177 commit
- github.com/taoeffect/empress#61 pull request
Is CVE-2014-125030 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
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.95% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
| CNA | 3.0 | 6.3 | CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
| CNA | 2.0 | 5.8 | AV:A/AC:L/Au:N/C:P/I:P/A:P |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- taoeffect Empress
Classification
References
-
github.com
/taoeffect/empress/pull/61
issue-tracking, third-party-advisory
-
github.com
/taoeffect/empress/commit/557e177d8a309d6f0f26de46efb38d43e000852d
patch, third-party-advisory
-
vuldb.com
/?id.217154
vdb-entry, technical-description, permissions-required, third-party-advisory
-
vuldb.com
/?ctiid.217154
signature, permissions-required, third-party-advisory
Sources
- CVE List CVE-2014-125030
- NVD CVE-2014-125030
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.