# CVE-2008-1860: Code injection in n/a

> Remote attackers with admin access can inject arbitrary PHP code into LokiCMS configuration files, leading to code execution.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-58rh-xrx9-j32v

## What is CVE-2008-1860?

CVE-2008-1860 is a critical code injection vulnerability in n/a, published on 17 Apr 2008. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Static code injection vulnerability in admin.php in LokiCMS 0.3.3 and earlier allows remote attackers to inject arbitrary PHP code into includes/Config.php via the default parameter.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2008-1860?

It affects 1 product.


Products: Lokicms Lokicms.

## How do I fix CVE-2008-1860?

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

## Is CVE-2008-1860 being exploited?

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

Public exploit code:

- LokiCMS 0.3.3 - Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-4662](https://insights.sbomify.com/CVE-2008-4662/): Path traversal in n/a (medium 6.8)
- [CVE-2008-6643](https://insights.sbomify.com/CVE-2008-6643/): Missing authorization in n/a (medium 5.0)
- [CVE-2008-5965](https://insights.sbomify.com/CVE-2008-5965/): Path traversal in n/a (medium 5.0)
- [CVE-2008-4913](https://insights.sbomify.com/CVE-2008-4913/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1860 and fix it if it is affected.

What it is: CVE-2008-1860 is a critical code injection vulnerability in n/a, published on 17 Apr 2008. 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-2008-1860 exists.

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-2008-1860/ (Markdown: https://insights.sbomify.com/CVE-2008-1860/index.md)
```

## Sources

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

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