The Bulk Media Register WordPress plugin before 2.01 does not properly validate a user-supplied path before moving a
Source GCVE Database
Not known to be exploited : upgrade to 2.01 soon.
Data as of 31 Oct 2026, 07:08 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 2.01
Exploitation evidence
Disclosed: evidence found.
CVE published 31 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade Bulk Media Register (WordPress plugin) to 2.01.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Bulk Media Register | Affected
| Fixed in
|
AI-suggested
A fix is available in Bulk Media Register plugin version 2.01. Users should upgrade to version 2.01 or later to remediate this vulnerability.
Description
The Bulk Media Register WordPress plugin versions before 2.01 contain a vulnerability where user-supplied file paths are not properly validated before moving files on the server. This flaw allows users with the Author role to move or rename arbitrary files, potentially outside the WordPress root directory, which can bypass directory-level access controls and expose protected files.