dbcve.org
Vk All In One Expansion UnitWordPress extension · Vektor Inc

CVE-2024-37956

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-20
Fix available
A fix is available. Upgrade to 9.99.2.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Vektor,Inc. VK All in One Expansion Unit allows Stored XSS.This issue affects VK All in One Expansion Unit: from n/a through 9.99.1.0.

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

A stored Cross-Site Scripting (XSS) vulnerability exists in the VK All in One Expansion Unit WordPress plugin. The vulnerability allows malicious JavaScript code to be injected and persisted in the database, which then executes when other users view affected pages. This stems from improper input sanitization and output escaping in web page generation.

MitigationUpgrade to version 9.99.1.1 or later. If immediate patching is not possible, disable or restrict user input fields within the plugin until the patch can be applied, as stored XSS can affect all site visitors.

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
Vk All In One Expansion UnitWordPress extension
Affected:< 9.99.2.0

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
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 checks

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

  1. Check the installed version of the VK All In One Expansion Unit plugin
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate 'VK All In One Expansion Unit' and note the version number displayed. Alternatively, access the server via FTP or file manager and check the plugin's main directory (typically wp-content/plugins/vk-all-in-one-expansion-unit/) for a style.css or readme.txt file containing the version metadata.
    Affected if The displayed version is lower than 9.99.2.0 (for example, 9.99.1.0, 9.98.0, or any version number below 9.99.2.0)
  2. Verify the plugin is active on the WordPress site
    In the WordPress admin dashboard under Plugins > Installed Plugins, confirm that VK All In One Expansion Unit shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is active and the version is below 9.99.2.0
  3. Identify if any VK All In One Expansion Unit features that accept user input are in use
    Review the site configuration and active modules within VK All In One Expansion Unit (typically found under the VK Block settings in the WordPress admin sidebar). Look for modules such as contact forms, comment sections, custom post type submissions, or any feature that stores and displays user-submitted content.
    Affected if Any plugin feature that accepts and stores user input is enabled, especially forms or content submission modules, while running a version below 9.99.2.0

The environment is affected if the VK All In One Expansion Unit plugin is installed, active, and running a version numbered lower than 9.99.2.0, particularly if any user input features are enabled.

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
Upgrade available Upgrade to 9.99.2.0 or later
Fixed in 9.99.2.0
Interim mitigation

Upgrade to version 9.99.1.1 or later. If immediate patching is not possible, disable or restrict user input fields within the plugin until the patch can be applied, as stored XSS can affect all site visitors.

Recommended fix High confidence

VK All In One Expansion Unit 9.99.2.0

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to WordPress Admin Dashboard > Plugins.
  3. 3. Find 'VK All In One Expansion Unit' in the installed plugins list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 9.99.2.0 or later.
  5. 5. Alternatively, go to Plugins > Add New > Upload and upload the latest version from the WordPress plugin repository.
  6. 6. After updating, verify the plugin version shows 9.99.2.0 or higher in the installed plugins list.
  7. 7. Test critical functionality on your site to ensure the update did not break existing features.

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

Fix this in Vk All In One Expansion Unit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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