# CVE-2026-49113: WordPress Cornerstone plugin < 7.8.8 - Arbitrary Code Execution vulnerability

> Subscribers can execute arbitrary code in the Cornerstone WordPress plugin, allowing attackers to compromise the site.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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:** 16 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** GHSA-qp4f-jv68-3xrf

## What is CVE-2026-49113?

CVE-2026-49113 is a high-severity code injection vulnerability in THEMECO Cornerstone, published on 16 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Subscriber Arbitrary Code Execution in Cornerstone < 7.8.8 versions.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-49113?


## How do I fix CVE-2026-49113?

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

## Is CVE-2026-49113 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49113 and fix it if it is affected.

What it is: CVE-2026-49113 is a high-severity code injection vulnerability in THEMECO Cornerstone, published on 16 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49113 in the wild and no public exploit code.

Affected product: THEMECO Cornerstone. 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-2026-49113/ (Markdown: https://insights.sbomify.com/CVE-2026-49113/index.md)
```

## Sources

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

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