Skip to main content

Photo Engine CVE-2026-115259

| EUVDEUVD-2026-112630 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-10-29 WPScan GHSA-38w6-cwxx-3m7p
4.9
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain Author-level WordPress account
  2. Delivery
    Call unauthorized REST API post-update route
  3. Exploit
    Supply arbitrary target post ID and fields
  4. Execution
    Overwrite another user's post content
  5. Impact
    Site content tampered/defaced

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Exploitation requires an authenticated WordPress account with Author-level capabilities or higher on a site running Photo Engine (Media Organizer & Lightroom) version 6.5.8 or earlier; the attacker then abuses one of the plugin's REST API routes that updates post data without verifying post ownership or authorization. No end-user interaction is needed (UI:N) and attack complexity is low (AC:L), but the account requirement is the key limiting factor - the flaw is not reachable by anonymous/unauthenticated visitors, so it primarily threatens multi-user sites that provision Author (or higher) roles to semi-trusted contributors. Impact is limited to integrity (modifying posts, pages and attachments); no data disclosure or denial of service results. Updating to 6.6.0 is the vendor fix.

Impact

This is a broken-authorization / IDOR flaw (CWE-639) in a WordPress plugin, and the signals consistently point to a moderate, not urgent, priority. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N, base 4.9) scores only integrity impact (I:H) with no confidentiality or availability effect, matching the description: an attacker can alter the title, content, excerpt and other fields of arbitrary posts/pages/attachments but cannot read protected data or take the site down. SSVC agrees with a low-urgency posture - Exploitation: none, Automatable: no, Technical Impact: partial - and the vuln.today Decision label is 'this_month', not act_now or emergency. There is no CISA KEV listing and no EPSS value supplied, so there is no evidence of active or widespread exploitation; a WPScan PoC reference exists but is not verified as working exploit code. One internal conflict should be verified: the input vector states PR:H (high privilege), yet the description requires only 'Author-level access and above', which in WordPress is a comparatively low-privilege role - this suggests the real privilege requirement is closer to PR:L, which would raise the honest base score slightly (to ~5.4) and make the vuln somewhat easier to reach than PR:H implies. Net: a genuine multi-user integrity/defacement risk on sites that hand out Author accounts, but not a drop-everything emergency.

Exploit ScenarioDerived

On a multi-author WordPress site running Photo Engine 6.5.8 or earlier, an attacker who holds (or has obtained) an Author-level account sends a crafted request to the plugin's vulnerable REST API route, which fails to check post ownership. They overwrite the title, body and excerpt of posts, pages or attachments owned by other users - enabling content tampering, defacement or insertion of malicious/SEO-spam content. A WPScan PoC reference exists but is not verified as working exploit code, and exploitation requires low complexity (AC:L) but a valid authenticated account.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 29, 2026

Broken authorization in the Photo Engine (Media Organizer & Lightroom) WordPress plugin through 6.5.8 allows authenticated users holding Author-level capabilities or higher to modify the title, content, excerpt and other fields of arbitrary posts, pages and attachments, including entries owned by other users. The flaw is a missing ownership/authorization check on one of the plugin's REST API routes; no user interaction is required and the impact is limited to integrity, with no disclosure or denial of service. A public PoC reference exists but is not verified as working exploit code, CISA SSVC records no known exploitation, and the vendor fix is version 6.6.0.

RemediationAI

Update the Photo Engine (Media Organizer & Lightroom) plugin to 6.6.0, the vendor-released fix, through the WordPress plugin updater or by following the WPScan advisory at https://wpscan.com/vulnerability/ef3a6287-bc56-464d-a13f-d3aee46a8df5/; the vendor reports a patch as available and no separate patched branch is listed. Because exploitation requires an Author-level account or higher, reducing the number of users holding Author and above roles, and reviewing which accounts have that capability, limits exposure while the update is staged - at the cost of restricting contributor publishing workflows. No other workaround or configuration-level mitigation is documented in the available sources, so the upgrade is the complete fix.

Affected VersionsENISA

Photo Engine (Media Organizer & Lightroom) 0 <6.6.0

Affected Packages

euvd photo_engine_media_organizer_lightroom fix: 6.6.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Photo Engine is a WordPress media organizer and Lightroom integration plugin that exposes REST API routes for managing post and attachment data. CVE-2026-115259 is CWE-639 (Authorization Bypass Through User-Controlled Key): the route that updates post data does not verify that the requesting user owns the target post or holds the capability required for that specific object, so an Author-level account can supply another user's post identifier and have fields rewritten. This is a broken object-level authorization (IDOR) condition rather than a true authentication bypass, even though it is tagged as an authentication bypass; the account prerequisite remains. The advisory does not publish the exact route path or parameter names, so the precise trigger is not described in the available sources. The CVE record lists CVSS 3.1 at 4.9 with PR:H, while the independent assessment uses PR:L (Author-level) with integrity-only impact; both agree on AV:N/AC:L/UI:N/S:U/C:N/I:H/A:N otherwise.

Know when Photo Engine Media Organizer Lightroom gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 4.9 MEDIUM
AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 6.5 MEDIUM

Remotely reachable REST route (AV:N/AC:L) requires a low-privilege authenticated Author role (PR:L, not PR:H), no user interaction, integrity-only impact (I:H; C:N/A:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

3
Patch available
Oct 29, 2026 - 07:01 EUVD
CVE Published
Oct 29, 2026 - 06:00 cve.org
MEDIUM 4.9
CVE Published
Oct 29, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Low
niche WordPress media-management/Lightroom plugin, limited install base
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +24
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy