# CVE-2018-1000509: Deserialization in n/a

> An admin can execute arbitrary code via unsafe deserialization in the Settings page AJAX handler of the Redirection plugin.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f85q-26xg-xvqx

## What is CVE-2018-1000509?

CVE-2018-1000509 is a high-severity unsafe deserialization vulnerability in n/a, published on 26 Jun 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Redirection version 2.7.1 contains a Serialisation vulnerability possibly allowing ACE vulnerability in Settings page AJAX that can result in could allow admin to execute arbitrary code in some circumstances. This attack appear to be exploitable via Attacker must have access to admin account. This vulnerability appears to have been fixed in 2.8.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Redirection Redirection.

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

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

## Is CVE-2018-1000509 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-1000504](https://insights.sbomify.com/CVE-2018-1000504/): Path traversal in n/a (high 7.2)
- [CVE-2011-5329](https://insights.sbomify.com/CVE-2011-5329/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2012-6717](https://insights.sbomify.com/CVE-2012-6717/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1000509 is a high-severity unsafe deserialization vulnerability in n/a, published on 26 Jun 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1000509 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-1000509/ (Markdown: https://insights.sbomify.com/CVE-2018-1000509/index.md)
```

## Sources

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

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