# CVE-2026-115259: Photo Engine < 6.6.0 - Author+ Arbitrary Content Modification via IDOR


- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-38w6-cwxx-3m7p

## What is CVE-2026-115259?

CVE-2026-115259 is a medium-severity vulnerability in Unknown Photo Engine (Media Organizer & Lightroom), published on 29 Oct 2026. 

### Official description

The Photo Engine (Media Organizer & Lightroom) WordPress plugin before 6.6.0 does not have proper authorization checks when updating post data through one of its REST API routes in all versions up to, and including, 6.5.8. This makes it possible for authenticated attackers, with Author-level access and above, to modify the title, content, excerpt and other fields of arbitrary posts, pages and attachments, including those belonging to other users.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-115259 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115259 is a medium-severity vulnerability in Unknown Photo Engine (Media Organizer & Lightroom), published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115259 in the wild and no public exploit code.

Affected product: Unknown Photo Engine (Media Organizer & Lightroom). 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-115259/ (Markdown: https://insights.sbomify.com/CVE-2026-115259/index.md)
```

## Sources

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

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