Skip to main content
CVE-2026-120575VulnerabilityPublished

The Photo Engine (Media Organizer & Lightroom) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-120575· Medium 6.4

Not known to be exploited · CVSS 6.4 Medium.

Data as of 3 Nov 2026, 07:29 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 monitor the vendor's advisory for updates. Until a fix is available, restrict subscriber-level access where possible and consider disabling or limiting use of the Photo Engine plugin. Review and harden authentication mechanisms related to the wplr_auth_token and ensure proper input sanitization and output escaping are implemented. Avoid exposing sensitive tokens in client-side scripts.

Description

The Photo Engine (Media Organizer & Lightroom) WordPress plugin versions up to and including 6.5.7 contain a stored cross-site scripting (XSS) vulnerability via the 'hierarchy[].name' parameter. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users view the affected pages. The vulnerability arises from insufficient input sanitization and output escaping, combined with an authentication mechanism that relies solely on a user meta token without proper capability checks. This token is exposed on admin pages due to a commented-out guard, increasing the risk of exploitation.

References

Community reviews

Loading reviews…