CVE-2014-125136
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2014-125136 is a high-severity Exposure of Backup File to an Unauthorized Control Sphere (CWE-530) vulnerability in Zeroscience (inferred from references). Its CVSS base score is 8.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique NTDS (T1003.003); ranked at the 36th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2014-9837
Vulnerability Data
C97net qEngine CMS through 6.0.0, Kemana Directory through 1.5.6, and Cart Engine through 3.0.0 contain an information disclosure vulnerability that exposes database backups in the web-accessible /admin/backup directory. Unauthenticated attackers can list the directory or guess date-based names like 'Full…
more
Backup YYYYMMDD.sql' to download dumps containing user records and administrator password hashes.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Enforces authorization checks on all logical access, directly stopping unauthorized actors from reaching backup files.
Limits privileges so that only the minimal set of users can access backup locations or archives.
Explicitly restricts access to removable or backup media to authorized personnel only.
Requires physical and logical controls plus encryption or access restrictions when storing backup media.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Explicit requirement to protect backups directly mitigates unauthorized exposure of backup files.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.3's access restriction mechanisms (per-identity rights, isolation, configuration controls) directly block unauthorized actors from reading the backup file even when it sits in a nominally accessible location; the remainder is bounded and nameable -- backup files whose access path bypasses the access control (e.g., served through a web server that does not honor the access rule, or accessible via a separate channel like an FTP share outside the controlled scope), where the clause's mechanism does not reach.
Access control directly limits who can reach backup files, though it does not address how backups are created or stored.
A.8.10 mandates deletion of obsolete versions, copies and temporary files wherever they are located, which removes the weakness for exposed backup files that are obsolete and contain sensitive information; however, it does not address backups that are still required (e.g., for disaster recovery) but misplaced in an accessible location, where the remedy is access control or relocation rather than deletion, leaving a nameable remainder.
A.8.12's data leakage prevention tools can block the network transmission or user action that exposes a backup file to an unauthorized control sphere, but the clause does not address the root cause of the file being stored in an accessible location in the first place, leaving the weakness present and exploitable through channels not monitored by DLP.
A.8.13 ensures backup copies exist and are recoverable; it does not govern where backup files are stored or who can access them, so an exposed backup file remains fully exploitable.