Skip to main content
VulnerabilityPublished

CVE-2026-120575: Photo Engine (Media Organizer & Lightroom) (WordPress plugin) · Cross-site Scripting

Affects Photo Engine (Media Organizer & Lightroom) (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.4 Medium.

Data as of 3 Nov 2026, 05:13 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.16.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
tigroumeowPhoto Engine (Media Organizer & Lightroom)Affected
  • <=6.5.7
Fixed in–

AI-suggested

Users should upgrade beyond version 6.5.7 when a fix is released. Until then, restrict subscriber-level access if possible and monitor for plugin updates. Because the vulnerability relies on authentication tokens exposed in admin pages and lack of capability checks, reviewing and hardening access controls and token handling may reduce risk.

Description

The Photo Engine (Media Organizer & Lightroom) WordPress plugin is vulnerable to stored cross-site scripting (XSS) via the 'hierarchy[].name' parameter in all versions up to and including 6.5.7. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users view the affected pages. This is enabled by insufficient input sanitization and output escaping, combined with an authentication mechanism that relies solely on a usermeta token without capability checks and exposure of the token on admin pages.

References

Community reviews

Loading reviews…