# CVE-2015-5227: Code injection in n/a

> Remote attackers can execute arbitrary code via the url parameter in the Landing Pages plugin for WordPress.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Oct 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c9pj-cm34-5483

## What is CVE-2015-5227?

CVE-2015-5227 is a high-severity code injection vulnerability in n/a, published on 18 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Landing Pages plugin before 1.9.2 for WordPress allows remote attackers to execute arbitrary code via the url parameter.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2015-5227?

It affects 1 product.


Products: Inboundnow Wordpress Landing Pages.

## How do I fix CVE-2015-5227?

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

## Is CVE-2015-5227 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5227 and fix it if it is affected.

What it is: CVE-2015-5227 is a high-severity code injection vulnerability in n/a, published on 18 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-5227 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-2015-5227/ (Markdown: https://insights.sbomify.com/CVE-2015-5227/index.md)
```

## Sources

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

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