CVE-2024-43346
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 Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Wow-Company Modal Window allows Stored XSS.This issue affects Modal Window: from n/a through 6.0.3.
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 stored XSS vulnerability exists in Wow-Company Modal Window plugin (versions through 6.0.3) where user-supplied input is not properly sanitized before being rendered in web pages. This allows malicious JavaScript code to be stored and executed when other users view affected modal windows.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.0.4CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Modal Window plugin is installedAccess WordPress admin panel, navigate to Plugins section, and look for 'Wow Company Modal Window' or 'Modal Window' by Wow-Company in the list of installed pluginsAffected if Plugin is present in the WordPress installation
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Modal Window, and view the version number displayed below the plugin name. Alternatively, check the plugin's main PHP file for the 'Version' header in the plugin comment blockAffected if Version number is less than 6.0.4 (versions 6.0.3 and below are affected)
-
Identify modal windows accepting user inputNavigate to Modal Window settings in WordPress admin (usually under a 'Modal Window' menu item created by the plugin). Review each modal configuration to identify which ones accept and display user-submitted content or external inputAffected if Any modal window is configured to display user-supplied input without additional server-side sanitization
-
Inspect modal content for suspicious scriptsView the source of published modal windows (via browser developer tools or page source). Look for <script> tags, javascript: URLs, or event handlers (onclick, onerror, etc.) within modal content that were not intentionally addedAffected if Unexpected JavaScript code or event handlers are present in modal window output
-
Review WordPress audit logsCheck WordPress activity logs or security plugins for recent changes to Modal Window configurations, particularly creation or modification of modal entries with unusual contentAffected if Recent modifications show unexpected HTML/script content in modal configurations
Environment is affected if Wow Company Modal Window plugin version is below 6.0.4 and modal windows are configured to display user-supplied content without additional sanitization.
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 · scoped6.0.4
Update the Modal Window plugin to the latest patched version. As a temporary measure, disable the plugin until an update is available.
6.0.4
- Log into the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the Modal Window plugin by Wow-Company
- If an update is available, click 'Update Now' to upgrade to version 6.0.4
- Alternatively, go to Plugins > Add New > Upload and upload version 6.0.4 of the plugin
- After updating, verify the plugin version shows 6.0.4 in the plugins list
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43346 — 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-2024-43346 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