WPScan says the plugin fails to verify a request authentication value and does not validate an uploaded file's path or type. An attacker can write arbitrary files to the server and may achieve remote code execution.WPScan says this flaw is being actively exploited and lists no known fix. Its entry was publicly published on 6 November 2026 and updated on 14 November. WordPress.org says the plugin was closed on 9 November, pending review; that notice does not state why it was closed.
What it allows
How Can CVE-2026-123751 Lead to Code Execution?
According to WPScan, the plugin does not properly verify a request authentication value before handling an upload. It also fails to validate where an uploaded file goes or what type it is. Together, those failures let an unauthenticated attacker write an arbitrary file to the server, with potential remote code execution.
WPScan explicitly reports active exploitation of CVE-2026-123751. Brandefense Blackhole counted two dark-chat posts mentioning this CVE from 17 August through 15 November 2026. The measured unit is posts, which does not establish a number of attacks or affected sites.
A GitHub search captured on 15 November 2026 found one public repository named CVE-2026-123751. Its description claims a proof of concept, but the code was not assessed. The CISA KEV snapshot dated 13 November did not list this CVE; catalog status does not override WPScan's exploitation statement.
How Does the Other WP Duplicate CVE Differ?
Patchstack assigns CVE-2026-39755 to an arbitrary file upload issue in WP Duplicate through 1.1.11. Its entry says Subscriber privileges are required. CVE-2026-123751 is the unauthenticated issue described by WPScan, so these entries have different stated access conditions.
The opened sources do not establish that both records describe the same code path. Do not transfer Patchstack's privilege requirement or 9.9 score to CVE-2026-123751. For CVE-2026-123751, use WPScan's unauthenticated access condition when prioritizing inventory and isolation.
Who is affected
Which Installations Are Exposed to CVE-2026-123751?
WPScan identifies WP Duplicate versions through 1.1.11 as affected. Its public entry gives no additional configuration condition and lists no known fix. Check WordPress inventories for the WP Duplicate plugin under its local-sync directory name and record the installed version on each site.
WordPress.org lists version 1.1.11 and shows active installations as N/A. That field cannot support an estimate of vulnerable websites. The directory says the plugin has been closed since 9 November 2026 and is unavailable for download pending review.
Prioritize sites reachable from untrusted networks, then remove the plugin or isolate the site after preserving evidence needed for investigation. Record the decision in the patch management process. For the broader workflow, see the vulnerability intelligence platform; the immediate action does not depend on a promised patch.
Timeline
- 2026-11-06
WPScan publicly published its CVE-2026-123751 vulnerability entry.
- 2026-11-09
NVD published the CVE record; WordPress.org dates the plugin directory closure to this day.
- 2026-11-14
WPScan last updated its public entry.
What to do
-
Find WP Duplicate installations
Inventory WordPress sites for the WP Duplicate plugin under local-sync. Record each installed version, site exposure, and responsible owner.
-
Remove or isolate the affected plugin
For versions through 1.1.11, preserve needed evidence, then remove the plugin or isolate the site. WPScan lists no known fix, so do not assume an update resolves this CVE.
-
Investigate exposed servers
Review web and server logs for suspicious upload activity and unexpected file changes. Inspect affected hosts for signs of code execution and scope any confirmed compromise.
-
Verify remediation
Recheck the site inventory and confirm the affected plugin is absent or the site remains isolated. If a vendor fix is later published, verify its version against the vendor notice before restoring exposure.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-123751 in Brandefense Atlas
The Atlas record of CVE-2026-123751: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-123751 require a WordPress account?
No. WPScan describes CVE-2026-123751 as an unauthenticated file upload vulnerability in WP Duplicate through version 1.1.11.
Is there a fixed version for CVE-2026-123751?
WPScan lists no known fix. WordPress.org shows 1.1.11 as the directory version and says the plugin was closed on 9 November 2026.
Is CVE-2026-39755 the same vulnerability as CVE-2026-123751?
The public entries give different privilege requirements. Patchstack requires Subscriber access for CVE-2026-39755, while WPScan calls CVE-2026-123751 unauthenticated. Their code-path relationship is unconfirmed.
What does WPScan say about exploitation of CVE-2026-123751?
WPScan reports active exploitation. Brandefense Blackhole counted two dark-chat posts mentioning this CVE from 17 August through 15 November 2026; those posts are discussion signals, not incident counts.