CVE-2026-1499
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WP Duplicate plugin for WordPress is vulnerable to Missing Authorization leading to Arbitrary File Upload in all versions up to and including 1.1.8. This is due to a missing capability check on the `process_add_site()` AJAX action combined with path traversal in the file upload functionality. This makes it possible for authenticated (subscriber-level) attackers to set the internal `prod_key_random_id` option, which can then be used by an unauthenticated attacker to bypass authentication checks and write arbitrary files to the server via the `handle_upload_single_big_file()` function, ultimately leading to remote code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP Duplicate WordPress plugin has a critical authorization bypass in its AJAX handler. An attacker with subscriber-level privileges can set an internal option (`prod_key_random_id`) via the unprotected `process_add_site()` AJAX action. This option is then leveraged by an unauthenticated attacker to bypass authentication and write arbitrary files via path traversal in `handle_upload_single_big_file()`, achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionNavigate to WordPress Admin > Plugins > Installed Plugins > WP Duplicate, or inspect the plugin main file header for the 'Version' commentAffected if Version is 1.1.8 or lower (1.1.8 is the last vulnerable version)
-
Verify AJAX action accessibilityCheck if the wp-admin/admin-ajax.php?action=process_add_site endpoint responds to requests; test with a low-privilege (subscriber) user account or check the plugin source for action registrationAffected if The process_add_site AJAX action is registered and accessible without capability checks
-
Confirm upload handler existsLocate the handle_upload_single_big_file() function in the plugin code, typically in an AJAX handler file or the main plugin fileAffected if The function handle_upload_single_big_file() is present in the plugin code (indicates the vulnerable upload path exists)
-
Check option value for prod_key_random_idQuery the WordPress options table (wp_options) for the option_name 'prod_key_random_id' - use SQL: SELECT * FROM wp_options WHERE option_name = 'prod_key_random_id'Affected if The prod_key_random_id option exists and contains a value set by a subscriber-level user (indicates exploitation attempt or successful exploitation)
-
Inspect upload directory for suspicious filesCheck the wp-content/uploads/ directory (or custom upload path) for recently created .php files with unusual names, especially in subdirectoriesAffected if Arbitrary .php files exist in upload directories that were not intentionally placed there by administrators
A user is affected if they have WP Duplicate plugin version 1.1.8 or lower installed and the vulnerable AJAX endpoint is accessible, allowing unauthorized file uploads.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to version 1.1.9 or later which adds capability checks to the AJAX action and proper validation of file upload paths. Until then, disable the plugin or restrict subscriber-level user registrations.
Latest version from WordPress plugin repository (version > 1.1.8)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the WP Duplicate plugin
- Check if an update is available and update to the latest version
- If no update is available via the WordPress admin, download the latest version from the WordPress plugin repository and manually upload/replace the plugin files
- Verify the updated version number is greater than 1.1.8 after updating
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1499 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1499 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data