dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-14158

HIGH · 8.8 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

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 Widget Logic Visual plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.52 via the widget_logic_visual_check_visibility function. This is due to missing capability check and nonce verification on the widget-logic-update-conditional-tags AJAX action combined with insufficient sanitization of the 'nwlv[cod-tag]' parameter before storage and subsequent use in an eval() call. This makes it possible for authenticated attackers, with subscriber-level access and above, to execute code on the server.

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 Widget Logic Visual WordPress plugin contains an authenticated Remote Code Execution vulnerability in versions up to 1.52. The AJAX action 'widget-logic-update-conditional-tags' lacks both capability checks and nonce verification, allowing any authenticated user (subscriber-level or higher) to inject PHP code through the unsanitized 'nwlv[cod-tag]' parameter. This data is stored and later executed via an eval() call, enabling complete server compromise.

MitigationUpdate the plugin to a patched version immediately. Until then, disable the plugin or restrict AJAX access at the server level. Audit all user accounts with subscriber-level access for compromise.

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 checks

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

  1. Verify the Widget Logic Visual plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Widget Logic Visual' in the list, or query the wp_options table for the option_name containing the plugin's stored settings
    Affected if The plugin appears in the installed plugins list and is active
  2. Determine the installed plugin version
    In the WordPress plugins list, click on the plugin to view details and note the version number displayed, or read the plugin header from the main plugin file
    Affected if The installed version is 1.52 or any version prior to this (the vulnerability affects versions up to 1.52)
  3. Confirm the AJAX endpoint is accessible
    Send a request to wp-admin/admin-ajax.php with action=widget-logic-update-conditional-tags. This can be done via curl or browser developer tools
    Affected if The AJAX endpoint returns a 200 response instead of 0 or an error, indicating the action is registered and callable
  4. Identify user roles with access
    In WordPress admin > Users, review the list of users and their assigned roles. Pay particular attention to users with Subscriber role, as this level is sufficient to exploit the flaw
    Affected if Any user account with Subscriber-level access or higher exists on the site
  5. Inspect stored conditional tag data for malicious content
    Query the wp_options table for options containing 'widget_logic' or similar plugin-related keys. Examine the stored value of the 'nwlv[cod-tag]' parameter for suspicious PHP code patterns such as eval(), base64_decode(), shell_exec(), or system()
    Affected if The stored conditional tag data contains PHP code that was not intentionally configured by an administrator

Your environment is affected if the Widget Logic Visual plugin is active, installed at version 1.52 or below, and the site has any authenticated user accounts, as the AJAX action can be exploited by any subscriber-level user to inject and execute arbitrary PHP code.

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 immediately. Until then, disable the plugin or restrict AJAX access at the server level. Audit all user accounts with subscriber-level access for compromise.

Recommended fix Moderate confidence

1.53 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Widget Logic Visual plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/widget-logic-visual/ and upload it manually
  6. 6. After updating, verify the plugin is active and functioning correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14158 — 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-14158 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