# CVE-2018-25184: Surreal ToDo 0.6.1.2 Local File Inclusion via index.php

> Unauthenticated attackers can read arbitrary system files via directory traversal in the content parameter of index.php.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-7p22-frc8-w9h8

## What is CVE-2018-25184?

CVE-2018-25184 is a medium-severity path traversal vulnerability in Getsurreal Surreal ToDo, published on 6 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Surreal ToDo 0.6.1.2 contains a local file inclusion vulnerability that allows unauthenticated attackers to read arbitrary files by manipulating the content parameter. Attackers can supply directory traversal sequences through the content parameter in index.php to access sensitive system files like configuration and initialization files.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2018-25184 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25184 is a medium-severity path traversal vulnerability in Getsurreal Surreal ToDo, published on 6 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25184 exists.

Affected product: Getsurreal Surreal ToDo. 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-25184/ (Markdown: https://insights.sbomify.com/CVE-2018-25184/index.md)
```

## Sources

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

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