# CVE-2026-87848: MPCX Lightbox 1.2.2 - 1.2.5 - Unauthenticated Non-Public Post Content Disclosure

> Unauthenticated attackers can retrieve content from private, draft, and password-protected posts via an unprotected AJAX action in the MPCX Lightbox plugin.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/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:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-c9c7-pp8h-rm54

## What is CVE-2026-87848?

CVE-2026-87848 is a low-severity missing authorization vulnerability in Unknown MPCX Lightbox, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The MPCX Lightbox WordPress plugin 1.2.2 through 1.2.5 does not have any authorisation or authentication on one of its AJAX actions available to unauthenticated users, nor does it check the status of the requested post, allowing unauthenticated visitors to retrieve the title, content or excerpt of arbitrary posts, including private, draft, pending, trashed and password-protected ones.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-87848 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87848 is a low-severity missing authorization vulnerability in Unknown MPCX Lightbox, published on 23 Sep 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-87848 in the wild and no public exploit code.

Affected product: Unknown MPCX Lightbox. 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-87848/ (Markdown: https://insights.sbomify.com/CVE-2026-87848/index.md)
```

## Sources

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

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