Bulk Media Register < 2.01 - Author+ Arbitrary File Move via Path Traversal
Affects Bulk Media Register before 2.01, where users with the Author role can move or rename arbitrary files. The fix is in version 2.01.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 2.01
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Bulk Media Register WordPress plugin is affected. A user with Author-level access can exploit improper path validation to move or rename arbitrary files on the server, including files outside the WordPress installation, which can bypass directory protections and expose sensitive files.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
The Bulk Media Register WordPress plugin before 2.01 does not properly validate a user-supplied path before moving a file on the server, allowing users with the Author role to move or rename arbitrary files, including outside the WordPress root, which can defeat directory-level access controls and disclose protected files.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Unknown Bulk Media Register
fixed in 2.01
References 1
Questions about CVE-2026-118043
What does this mean?
Users with the Author role can move or rename arbitrary files, including files outside the WordPress root. This can defeat directory-level access controls and expose protected files.Source: wpscan.com
Am I affected, and how do I check?
The Bulk Media Register plugin before version 2.01 is affected. To check the installed version, look at the plugin's version number on the Plugins screen in the WordPress admin.Source: wpscan.com
What should I do about it?
Update Bulk Media Register to version 2.01 or later, which contains the fix.Source: wpscan.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data