Skip to main content
Menu
CVEs

WP Duplicate unauthenticated arbitrary file read in file_name parameter

CVE-2026-14491EUVD-2026-129503GHSA-QJ83-C39J-7G5PPublished November 19, 2026, updated

7.5HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The WP Duplicate – WordPress Migration Plugin for WordPress lets an attacker remotely, without logging in, read the contents of arbitrary files on the server, which can include sensitive information. The attacker gets past the login check by sending a JSON boolean `true` in place of the secret key value.

Written by a model

Original description

The WP Duplicate – WordPress Migration Plugin plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.1.11 via the 'file_name' parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. The authentication bypass requires submitting the JSON boolean true as the prod_key_random_id value, which coerces against any non-empty stored secret so that the loose != comparison evaluates to false, skipping the rejection branch entirely without knowledge of the secret.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-14491 (WP Duplicate <= 1.1.11 - Unauthenticated Arbitrary File Read via 'file_name' Parameter via Type-Juggling Auth Bypass), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-14491 (entry last updated 2026-11-19):
Affected:
- revmakx WP Duplicate – WordPress Migration Plugin: through 1.1.11
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-14491 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-14491 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/4d3a5a4b-bd29-418c-a204-f0ed9afb03fb?source=cve
- https://plugins.trac.wordpress.org/browser/local-sync/tags/1.1.11/includes/class-local-sync.php#L221
- https://plugins.trac.wordpress.org/browser/local-sync/tags/1.1.11/includes/class-local-sync-handle-server-requests.php#L467
- https://plugins.trac.wordpress.org/browser/local-sync/tags/1.1.11/includes/class-local-sync-handle-server-requests.php#L39
- https://plugins.trac.wordpress.org/browser/local-sync/tags/1.1.11/includes/class-local-sync-handle-server-requests.php#L134
- https://plugins.trac.wordpress.org/browser/local-sync/tags/1.1.11/admin/class-local-sync-admin.php#L1064
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-14491
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-14491"}.

Affected versions

cve.now Index

33Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 38 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 8

Questions about CVE-2026-14491

Is CVE-2026-14491 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

Which versions are affected by CVE-2026-14491?

WP Duplicate – WordPress Migration Plugin: through 1.1.11.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.