# CVE-2008-7125: Command injection in n/a

> Authenticated users can execute arbitrary shell commands in Ariadne web application via the annotate command.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pc8j-pfcg-w3f2

## What is CVE-2008-7125?

CVE-2008-7125 is a critical command injection vulnerability in n/a, published on 31 Aug 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

pphoto in Ariadne before 2.6 allows remote authenticated users with certain privileges to execute arbitrary shell commands via vectors related to PINP programs and the annotate command.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Ariadne-Cms Ariadne Cms.

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

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

## Is CVE-2008-7125 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-7125 is a critical command injection vulnerability in n/a, published on 31 Aug 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-7125 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-2008-7125/ (Markdown: https://insights.sbomify.com/CVE-2008-7125/index.md)
```

## Sources

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

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