# CVE-2018-15877: Command injection in n/a

> Attackers can execute arbitrary OS commands via the ip parameter in the Plainview Activity Monitor WordPress plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 26 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9x2f-2wff-79qv

## What is CVE-2018-15877?

CVE-2018-15877 is a high-severity command injection vulnerability in n/a, published on 26 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Plainview Activity Monitor plugin before 20180826 for WordPress is vulnerable to OS command injection via shell metacharacters in the ip parameter of a wp-admin/admin.php?page=plainview_activity_monitor&tab=activity_tools request.

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

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

It affects 1 product.


Products: Plainview Activity Monitor Project Plainview Activity Monitor.

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

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

## Is CVE-2018-15877 being exploited?

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

Public exploit code:

- Wordpress Plainview Activity Monitor Plugin RCE (20161228) (github_poc): https://github.com/Cinnamon1212/CVE-2018-15877-RCE
- Wordpress Plainview Activity Monitor RCE (metasploit)
- WordPress Plugin Plainview Activity Monitor 20161228 - (Authenticated) Command Injection (exploitdb)
- cve-2018-15877 (github_poc): https://github.com/cved-sources/cve-2018-15877
- WordPress Plugin Plainview Activity Monitor 20161228 - Remote Code Execution (RCE) (Authenticated) (2) (exploitdb)
- WP Plainview Activity Monitor auth RCE fix: broken manual cookie parse to stable Session handling. CVE-2018-15877 educational fix. (github_poc): https://github.com/firasotoom85-droid/wp-plainview-auth-RCE-broken-cookie-to-session-fix

## Fix prompt for AI coding agents

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

What it is: CVE-2018-15877 is a high-severity command injection vulnerability in n/a, published on 26 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-15877 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-2018-15877/ (Markdown: https://insights.sbomify.com/CVE-2018-15877/index.md)
```

## Sources

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

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