Skip to main content
VulnerabilityPublished

CVE-2026-120738: Organize Media Folder (WordPress plugin) · Cross-site Scripting

Affects Organize Media Folder (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.4 Medium.

Data as of 21 Nov 2026, 08:01 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 21 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 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
katsushi-kawamoriOrganize Media FolderAffected
  • <=2.00
Fixed in–

AI-suggested

Users should review their plugin configurations, especially the use of bbPress and gd-bbpress-attachments allowing frontend uploads by subscribers. Restricting upload permissions and disabling frontend attachment uploads for low-privilege users can mitigate exploitation risk. Monitor vendor advisories for any forthcoming official fixes. Until a patch is available, avoid granting upload capabilities to subscriber-level users or upgrade to a fixed version if released.

Description

The Organize Media Folder WordPress plugin up to version 2.00 is vulnerable to stored cross-site scripting (XSS) via the EXIF.DateTimeOriginal parameter. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users view the affected pages. Exploitation at subscriber level requires bbPress and gd-bbpress-attachments to be installed and configured to allow frontend attachment uploads. Without this configuration, author-level access is needed. The vulnerability arises from insufficient input sanitization and output escaping, bypassing WordPress's usual content filtering mechanisms.

References

Community reviews

Loading reviews…