# CVE-2026-14158: Widget Logic Visual <= 1.52 - Authenticated (Subscriber+) Remote Code Execution via 'nwlv[cod-tag]' Parameter

> Authenticated subscribers can execute arbitrary code on the server via an unsanitized parameter in the Widget Logic Visual WordPress plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-q799-r857-2h8x

## What is CVE-2026-14158?

CVE-2026-14158 is a high-severity code injection vulnerability in totalbounty Widget Logic Visual, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-14158?


## How do I fix CVE-2026-14158?

No fix has been published for CVE-2026-14158 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14158 being exploited?

There is no known exploitation of CVE-2026-14158 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14158 and fix it if it is affected.

What it is: CVE-2026-14158 is a high-severity code injection vulnerability in totalbounty Widget Logic Visual, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14158 in the wild and no public exploit code.

Affected product: totalbounty Widget Logic Visual. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14158/ (Markdown: https://insights.sbomify.com/CVE-2026-14158/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14158
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14158
- OSV: https://osv.dev/vulnerability/CVE-2026-14158

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14158/
Summaries are generated and may contain mistakes; the official description above is the record.