Vk All In One Expansion UnitWordPress extension · Vektor Inc
CVE-2023-28367
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 · uneditedCross-site scripting vulnerability in CTA post function of VK All in One Expansion Unit 9.88.1.0 and earlier allows a remote authenticated attacker to inject an arbitrary script.
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 confidenceStored XSS vulnerability in the CTA (Call to Action) post function of the VK All in One Expansion Unit WordPress plugin versions 9.88.1.0 and earlier. An authenticated attacker with access to the CTA post function can inject malicious JavaScript that executes when other users view the affected content.
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
< 9.88.2.0CVSS 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 VK All in One Expansion Unit is installedLog into WordPress admin, navigate to Plugins > Installed Plugins, and look for 'VK All in One Expansion Unit' in the list.Affected if The plugin is installed and active.
-
Check the installed version numberIn the Plugins list, find VK All in One Expansion Unit and note the version number displayed below the plugin name. Compare this version to 9.88.2.0.Affected if The installed version is 9.88.1.0 or earlier (any version below 9.88.2.0).
-
Determine if the CTA post function is accessibleNavigate to the plugin settings or check user role capabilities. The CTA post function is typically found in the plugin's post creation or template settings area. Verify which user roles have access to create or edit CTA posts.Affected if Untrusted or low-privilege users (such as Authors or Contributors) have access to the CTA post function.
-
Inspect existing CTA post entries for suspicious contentIf the plugin stores CTA posts as a custom post type, go to that section in the WordPress admin (usually under a menu item like 'CTA' or 'Call to Action'). Review the content of existing entries for unexpected script tags, javascript: URLs, or event handler attributes.Affected if Any CTA posts contain malicious JavaScript code such as <script> tags, onload/onerror attributes, or javascript: URIs.
A user is affected if the VK All in One Expansion Unit plugin is installed with version 9.88.1.0 or earlier and the CTA post function is accessible to untrusted users or already contains malicious scripts.
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 · scoped9.88.2.0
Update VK All in One Expansion Unit to the latest version (after 9.88.1.0) which contains the patched code. If immediate update is not possible, restrict administrative access to the CTA post function to trusted users only.
9.88.2.0
- Back up your WordPress site before performing any updates
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Find 'VK All In One Expansion Unit' in the plugin list
- Check for an available update and click 'Update Now' to upgrade to version 9.88.2.0 or later
- Alternatively, download the latest version from the WordPress Plugin Directory or vendor website
- Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
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
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28367 — 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-2023-28367 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