Skip to main content

Photo Engine CVE-2026-111971

| EUVDEUVD-2026-108016 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-22 WPScan GHSA-9g52-cg59-7f5p
6.8
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

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

  1. Access
    Authenticate as author-level user
  2. Exploit
    Store script in collection/gallery name
  3. Execution
    Administrator opens dashboard, payload executes
  4. Impact
    Perform actions as administrator

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a pre-authenticated account with the author role or above on the target WordPress site; the attacker supplies a crafted collection or gallery name that is stored without sanitisation/escaping. Execution is gated on user interaction: the injected script only fires when an administrator (or other privileged user) subsequently views the administrative dashboard where the name is rendered. Exploitation is limited to installations of Photo Engine (Media Organizer & Lightroom) before version 6.5.8 and to sites that actually grant author-or-higher accounts to untrusted users; single-admin sites face little practical exposure.

Impact

This is a moderate-priority stored XSS (CWE-79) in a WordPress plugin, not a high-urgency emergency. Key signals point to limited real-world risk: exploitation requires an authenticated account at the author role or above (per the description), there is no CISA KEV listing, no EPSS probability was supplied, and the only exploit artifact is an unverified WPScan PoC reference. The vuln.today decision label is 'this_month', consistent with a patch-when-convenient rather than drop-everything posture. There is a notable conflict in the supplied signals: the input CVSS vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H (base 6.8), but PR:H contradicts the description, which only requires the lower-privileged author role (normally PR:L), and the S:U with C:H/I:H/A:H is atypically high for a stored XSS whose payload merely executes in an administrator's browser - verify the metrics with WPScan/NVD. Because the flaw requires a pre-authenticated low-trust user and administrator interaction, it is primarily a privilege-escalation path on multi-author sites rather than a mass-exploitable internet-facing bug.

Exploit ScenarioDerived

On a multi-author WordPress site running Photo Engine before 6.5.8, a user holding the author role creates a collection or gallery whose name contains a malicious script payload. When an administrator later views the affected administrative dashboard, the stored script executes in the admin's authenticated browser session, enabling account takeover or further privilege escalation. A public PoC reference exists (WPScan) but it is not verified as working exploit code.

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

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

Alert me

AnalysisAIv1 – Oct 22, 2026

Stored cross-site scripting in the Photo Engine (Media Organizer & Lightroom) WordPress plugin before 6.5.8 allows authenticated users with author-level access or higher to save collection and gallery names containing script, which is stored unsanitised and rendered unescaped in the administrative dashboard. The injected code only executes when a privileged user, typically an administrator, later views that dashboard, so successful abuse requires a site that grants author-or-higher accounts to untrusted parties; single-admin installations face little practical exposure. A public PoC reference exists but is not verified as working exploit code, there is no confirmed active exploitation, and the vendor patch is available in 6.5.8.

RemediationAI

Update the Photo Engine (Media Organizer & Lightroom) plugin to 6.5.8 or later, which is the first version outside the affected range and the fix released by the vendor; verify the installed version string after upgrading since the CPE data carries no version constraints. If the update cannot be applied immediately, the exposure can be bounded by the prerequisite the flaw depends on: audit and restrict author-or-higher accounts so that only trusted users can create or rename collections and galleries, and review existing collection and gallery names for injected markup, noting that these measures reduce but do not eliminate the risk because a single compromised or malicious author account reintroduces the payload. Where author access cannot be trusted and patching is delayed, disabling the plugin removes the affected storage and dashboard rendering path at the cost of losing media-organizer functionality. Advisory details are available at https://wpscan.com/vulnerability/b1b9a655-6a1b-43d9-99ba-7734107465d6/ and https://nvd.nist.gov/vuln/detail/CVE-2026-111971.

Affected VersionsENISA

Photo Engine (Media Organizer & Lightroom) 0 <6.5.8

Affected Packages

euvd photo_engine_media_organizer_lightroom fix: 6.5.8

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

The flaw is CWE-79 (cross-site scripting) in a WordPress plugin that manages media collections and galleries. Input supplied in collection and gallery names is neither sanitised on storage nor escaped on output when the values are rendered in an administrative dashboard view, so script content persists in the database and executes in the browser session of any privileged user who loads that page. Exploitation prerequisites follow from the plugin's role model: the attacker must already hold an author-or-higher account on the target site, and code execution is gated on a separate privileged user interacting with the affected dashboard. The CPE record lists the vendor as unknown (cpe:2.3:a:unknown:photo_engine_(media_organizer_&_lightroom)) with no granular version wildcards, so version confirmation must come from the plugin's own version string; EUVD records the affected range as 0 through versions below 6.5.8. The independent assessment scores the issue at CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (scope changed, limited confidentiality and integrity impact), which is lower than the 6.8 source score because the practical requirement for an existing author account and administrator interaction bounds real-world impact.

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 6.8 MEDIUM
AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 5.4 MEDIUM

Author-level account needed (PR:L), admin must view the dashboard (UI:R), payload executes in a different security context so scope changes (S:C), with limited confidentiality/integrity impact typical of stored XSS.

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

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

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

Lifecycle Timeline

4
CVSS changed
Oct 22, 2026 - 11:22 NVD
6.8 (MEDIUM)
Patch available
Oct 22, 2026 - 07:01 EUVD
CVE Published
Oct 22, 2026 - 06:00 cve.org
MEDIUM 6.8
CVE Published
Oct 22, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The Photo Engine (Media Organizer & Lightroom) WordPress plugin before 6.5.8 does not sanitise and escape collection and gallery names before storing them and outputting them in an administrative dashboard, allowing authenticated users with the author role and above to perform Stored Cross-Site Scripting attacks.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Low
niche WordPress media/gallery plugin, limited installation base
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

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.2%
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
Total

Priority Score

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

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

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