# CVE-2025-1465: lmxcms Maintenance db.inc.php code injection

> Remote attackers can execute arbitrary code in lmxcms via the Maintenance component, though exploitation is difficult and requires permissions.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2025
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-4jjw-p5j8-wcgh

## What is CVE-2025-1465?

CVE-2025-1465 is a low-severity code injection vulnerability in lmxcms, published on 19 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, was found in lmxcms 1.41. Affected is an unknown function of the file db.inc.php of the component Maintenance. The manipulation leads to code injection. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-1465?

It affects 1 product.


Products: Lmxcms Lmxcms.

## How do I fix CVE-2025-1465?

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

## Is CVE-2025-1465 being exploited?

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

## Other vulnerabilities in lmxcms

- [CVE-2021-35437](https://insights.sbomify.com/CVE-2021-35437/): SQL injection in n/a (critical 9.8)
- [CVE-2023-46958](https://insights.sbomify.com/CVE-2023-46958/): Code injection in n/a (critical 9.8)
- [CVE-2023-29598](https://insights.sbomify.com/CVE-2023-29598/): SQL injection in n/a (critical 9.8)
- [CVE-2023-23136](https://insights.sbomify.com/CVE-2023-23136/): Path traversal in n/a (medium 6.5)
- [CVE-2023-1321](https://insights.sbomify.com/CVE-2023-1321/): lmxcms AcquisiAction.class.php update sql injection (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1465 and fix it if it is affected.

What it is: CVE-2025-1465 is a low-severity code injection vulnerability in lmxcms, published on 19 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1465 exists.

Affected product: lmxcms. 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-2025-1465/ (Markdown: https://insights.sbomify.com/CVE-2025-1465/index.md)
```

## Sources

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

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