dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3279

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Enable jQuery Migrate Helper plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `downgrade_jquery_version()` function in all versions up to, and including, 1.4.1. This is due to the function only verifying a nonce without checking user capabilities. This makes it possible for authenticated attackers, with Subscriber-level access and above, to downgrade the site-wide jQuery version from 3.7.1 to the legacy 1.12.4-wp release, which has knowns security vulnerabilities.

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 confidence

The Enable jQuery Migrate Helper plugin for WordPress has a missing capability check in the downgrade_jquery_version() function. The function only validates a nonce but does not verify user capabilities, allowing any authenticated user with Subscriber-level access or higher to trigger a site-wide jQuery downgrade from version 3.7.1 to the legacy 1.12.4-wp release, which contains known security vulnerabilities.

MitigationUpdate the plugin to a patched version that implements proper capability checks (e.g., 'manage_options') before executing the downgrade function, or remove the plugin if not required.

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Enable jQuery Migrate Helper plugin is installed
    Check the WordPress plugins directory or use wp-cli: wp plugin list --status=active --field=name | grep -i 'jquery-migrate-helper'
    Affected if The plugin is installed and active, making the vulnerability accessible
  2. Identify the installed plugin version
    Review the plugin header in main PHP file (enable-jquery-migrate-helper.php) or run: wp plugin get enable-jquery-migrate-helper --field=version
    Affected if Version is before the patched release that adds proper capability checks (the vulnerability exists in unpatched versions)
  3. Confirm presence of authenticated user accounts
    Query user roles in WordPress: wp user list --role=subscriber --field=user_login --count or check Users > All Users in admin for any accounts with Subscriber, Contributor, Author, Editor, or Administrator roles
    Affected if At least one user account with Subscriber-level access or higher exists, creating an attack vector
  4. Inspect loaded jQuery version in the browser
    Open browser console and run: jQuery.fn.jquery or check page source for wp-includes/js/jquery/jquery.js?ver= loaded version
    Affected if jQuery version shows 1.12.4-wp (the legacy vulnerable version) rather than 3.7.1, indicating the downgrade occurred

User is affected if the Enable jQuery Migrate Helper plugin is active with an unpatched version AND any authenticated user account with Subscriber-level access or higher exists in the WordPress installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a patched version that implements proper capability checks (e.g., 'manage_options') before executing the downgrade function, or remove the plugin if not required.

Recommended fix Moderate confidence

1.4.2 or later (check WordPress plugin repository for latest stable release)

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Enable jQuery Migrate Helper' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the updated version number is greater than 1.4.1
  6. 6. Confirm the plugin is functioning correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3279 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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