dbcve.org
Vk BlocksWordPress extension · Vektor Inc

CVE-2023-27923

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-23
Fix available
A fix is available. Upgrade to 1.53.0.1 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
Cross-site scripting vulnerability in Tag edit function of VK Blocks 1.53.0.1 and earlier and VK Blocks Pro 1.53.0.1 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 confidence

A cross-site scripting (XSS) vulnerability exists in the Tag edit function of VK Blocks and VK Blocks Pro plugins (versions 1.53.0.1 and earlier). The vulnerability allows an authenticated remote attacker to inject arbitrary JavaScript code through unsanitized input in the Tag edit functionality.

MitigationUpgrade to VK Blocks 1.53.1.0 or later and VK Blocks Pro 1.53.1.0 or later to receive the patch that adds proper input sanitization and output encoding in the Tag edit function.

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 BlocksWordPress extension
Affected:< 1.53.0.1

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 if VK Blocks plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'VK Blocks' or 'VK Blocks Pro' in the list. Alternatively, check the /wp-content/plugins/ directory for vk-blocks or vk-blocks-pro folders.
    Affected if Either VK Blocks or VK Blocks Pro plugin is present in the WordPress installation
  2. Identify the installed version of VK Blocks
    In WordPress admin > Plugins > Installed Plugins, click on the VK Blocks plugin to view the version number displayed in the plugin details. Alternatively, check the main plugin file (e.g., vk-blocks/index.php) for the 'Version:' header in the plugin comment block.
    Affected if The version is 1.53.0.1 or any version earlier than 1.53.0.1
  3. Determine if Tag edit functionality is accessible
    In WordPress admin, navigate to the VK Blocks settings or check if the Tag edit feature is available. This typically involves accessing Posts > Tags or a VK Blocks-specific taxonomy settings page where tags can be created or edited.
    Affected if The user has access to WordPress admin and the Tag edit/create interface is present and functional
  4. Verify WordPress user authentication status
    Confirm that the person accessing the Tag edit function has authenticated WordPress user credentials. Check if the user is logged in and has at least contributor-level access to create or edit tags.
    Affected if An authenticated WordPress user with access to the Tag edit function exists in the system

A user is affected if VK Blocks or VK Blocks Pro version 1.53.0.1 or earlier is installed and an authenticated user has access to the Tag edit functionality in WordPress admin.

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 1.53.0.1 or later
Fixed in 1.53.0.1
Interim mitigation

Upgrade to VK Blocks 1.53.1.0 or later and VK Blocks Pro 1.53.1.0 or later to receive the patch that adds proper input sanitization and output encoding in the Tag edit function.

Recommended fix Moderate confidence

VK Blocks 1.53.0.1 or later (VK Blocks Pro 1.53.0.1 or later)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'VK Blocks' (and 'VK Blocks Pro' if installed) in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository or from www.vektor-inc.co.jp
  6. 6. After updating, verify the plugin version is 1.53.0.1 or later

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

Fix this in Vk Blocks Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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 locally
dbcve dependency scanner

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