# CVE-2018-18487: Information disclosure in n/a

> Predictable backup filenames in Gxlcms allow attackers to locate and access sensitive database backups.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-p723-226c-99cr

## What is CVE-2018-18487?

CVE-2018-18487 is a high-severity vulnerability in n/a, published on 18 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In \lib\admin\action\dataaction.class.php in Gxlcms v2.0, the database backup filename generation uses mt_rand() unsafely, resulting in predictable database backup file locations.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-18487?

It affects 1 product.


Products: Gxlcms Gxlcms.

## How do I fix CVE-2018-18487?

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

## Is CVE-2018-18487 being exploited?

There is no known exploitation of CVE-2018-18487 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-20975](https://insights.sbomify.com/CVE-2020-20975/): SQL injection in n/a (critical 9.8)
- [CVE-2018-18488](https://insights.sbomify.com/CVE-2018-18488/): SQL injection in n/a (critical 9.8)
- [CVE-2018-14685](https://insights.sbomify.com/CVE-2018-14685/): Path traversal in n/a (critical 9.8)
- [CVE-2018-15177](https://insights.sbomify.com/CVE-2018-15177/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-14979](https://insights.sbomify.com/CVE-2017-14979/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-18487 and fix it if it is affected.

What it is: CVE-2018-18487 is a high-severity vulnerability in n/a, published on 18 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18487 in the wild and no public exploit code.

Affected product: n/a. 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-2018-18487/ (Markdown: https://insights.sbomify.com/CVE-2018-18487/index.md)
```

## Sources

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

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