# CVE-2026-9842: Backstage <= 1.4.2 - Unauthenticated Privilege Escalation via Permissive Demo Role Capabilities

> Unauthenticated attackers can escalate privileges by exploiting excessive capabilities in the Backstage Customizer Demo Access plugin for WordPress.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-xwxr-p855-gjc3

## What is CVE-2026-9842?

CVE-2026-9842 is a high-severity vulnerability in pixelgrade Backstage – Customizer Demo Access, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Backstage - Customizer Demo Access plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.4.2. This is due to the plugin assigning the `manage_options` capability to the `backstage_customizer_user` demo role, which is more permissive than necessary for Customizer-only demo access. This makes it possible for unauthenticated attackers to navigate beyond the Customizer and update arbitrary WordPress options such as `default_role`, leading to privilege escalation.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-9842 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9842 is a high-severity vulnerability in pixelgrade Backstage – Customizer Demo Access, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9842 in the wild and no public exploit code.

Affected product: pixelgrade Backstage – Customizer Demo Access. 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-9842/ (Markdown: https://insights.sbomify.com/CVE-2026-9842/index.md)
```

## Sources

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

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