CVE-2026-32367
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in Yannick Lefebvre Modal Dialog modal-dialog allows Remote Code Inclusion.This issue affects Modal Dialog: from n/a through <= 3.5.16.
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 · moderate confidenceA code injection vulnerability in the Yannick Lefebvre Modal Dialog WordPress plugin (versions <=3.5.16) allows remote attackers to include and execute arbitrary server-side code through improper control of code generation. The vulnerability stems from insufficient validation of user-supplied input used in dynamic file inclusion mechanisms, enabling unauthenticated 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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.
-
Identify if Modal Dialog plugin is installedNavigate to WordPress admin > Plugins > Installed Plugins and look for 'Modal Dialog' by Yannick Lefebvre, or inspect the plugin directory /wp-content/plugins/modal-dialog/ for the plugin folderAffected if The Modal Dialog plugin is present in the WordPress installation
-
Determine the installed plugin versionCheck the plugin main file (usually modal-dialog.php) for the version comment header, or view the plugin details in the WordPress admin plugins listAffected if The reported version is 3.5.16 or lower (any version <=3.5.16)
-
Verify the dynamic file inclusion endpoint exists and is accessibleInspect plugin source code for dynamic include/require statements using user-supplied parameters (commonly __FILE__, $_GET, or similar), then attempt to access the suspected inclusion endpoint via HTTP request to confirm it respondsAffected if The plugin contains dynamic file inclusion logic using unsanitized user input AND the endpoint is reachable without authentication
-
Confirm the plugin is activeCheck the WordPress admin plugins list or database wp_options table for active_plugins setting to verify Modal Dialog is enabledAffected if The plugin is actively enabled on the WordPress site (inactive plugins may still be vulnerable but are not actively exposed)
A user is affected if the Modal Dialog plugin version is 3.5.16 or lower, the plugin is enabled, and the vulnerable dynamic file inclusion mechanism is accessible to unauthenticated users.
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.
From vendor dataUpgrade to the latest version of Modal Dialog when available. If no patch exists, disable or remove the plugin immediately and review server-side file inclusion logic for proper input validation and allowlist-based controls.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32367 — 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-32367 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