# CVE-2014-125136: C97net qEngine CMS through 6.0.0, Kemana Directory through 1.5.6, and Cart Engine through 3.0.0 contain an information disclosure vulnerabil


- **Severity:** High 8.2 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-hhvm-rp85-j9hh

## What is CVE-2014-125136?

CVE-2014-125136 is a high-severity vulnerability in C97net Cart Engine, published on 28 Oct 2026. 

### Official description

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 Backup YYYYMMDD.sql' to download dumps containing user records and administrator password hashes.

Weakness: CWE-530 (Exposure of Backup File to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2014-125136?


## How do I fix CVE-2014-125136?

No fix has been published for CVE-2014-125136 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-125136 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-125136 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-125136 and fix it if it is affected.

What it is: CVE-2014-125136 is a high-severity vulnerability in C97net Cart Engine, published on 28 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-125136 exists.

Affected product: C97net Cart Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-125136/ (Markdown: https://insights.sbomify.com/CVE-2014-125136/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-125136
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-125136
- OSV: https://osv.dev/vulnerability/CVE-2014-125136

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-125136/
Summaries are generated and may contain mistakes; the official description above is the record.