Vayu BlocksWordPress extension · Themehunk
CVE-2025-22644
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 ('Cross-site Scripting') vulnerability in ThemeHunk Vayu Blocks – Gutenberg Blocks for WordPress & WooCommerce vayu-blocks allows Stored XSS.This issue affects Vayu Blocks – Gutenberg Blocks for WordPress & WooCommerce: from n/a through <= 1.4.7.
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 confidenceA stored Cross-site Scripting (XSS) vulnerability exists in the ThemeHunk Vayu Blocks WordPress plugin where user-supplied input is not properly sanitized before being stored and later rendered in web pages. Attackers with contributor-level access or higher can inject malicious JavaScript that executes in browsers of users viewing the affected Gutenberg blocks.
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
Vayu BlocksWordPress extension
<= 1.4.3CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
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.
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find ThemeHunk Vayu Blocks. Note the version number displayed. Alternatively, check the plugin header in /wp-content/plugins/vayu-blocks/vayu-blocks.php for the 'Version' field.Affected if The installed version is 1.4.3 or lower (any version <= 1.4.3).
-
Identify if Gutenberg blocks from the plugin are in useCheck published pages/posts for blocks with the 'ThemeHunk' or 'Vayu Blocks' prefix in the block selector (e.g., Vayu Button, Vayu Heading, Vayu Container). Inspect page content in the block editor or view page source for CSS classes or block markup containing 'wp-block-vayu-'.Affected if Any Vayu Blocks Gutenberg blocks are present in published content and the plugin version is <= 1.4.3.
-
Verify user registration and contributor accessGo to WordPress Settings > General and check if 'Membership' is enabled (Anyone can register). Then go to Users > All Users and review which roles exist. Check if any untrusted users have the Contributor role.Affected if User registration is enabled and/or untrusted Contributor-level users exist on the site while running a vulnerable plugin version.
You are affected if the installed version is 1.4.3 or lower AND the plugin Gutenberg blocks are being used on the site, especially with Contributor-level or higher users having access.
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 version 1.4.8 or later. Until patched, restrict user registration and carefully audit user permissions. Implement output encoding using wp_kses and esc_html/escape functions on any user-generated content rendered by the plugin.
Fix this in Vayu Blocks
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22644 — 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-2025-22644 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