GutenkitWordPress extension · Wpmet
CVE-2025-46253
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 Ataur R GutenKit gutenkit-blocks-addon allows Stored XSS.This issue affects GutenKit: from n/a through <= 2.2.2.
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 confidenceStored XSS vulnerability in GutenKit WordPress plugin allows attackers to inject malicious JavaScript through unsanitized user input that gets stored in the database and executed 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
GutenkitWordPress extension
< 2.2.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
- 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 GutenKit plugin is installedNavigate to WordPress admin dashboard > Plugins section and locate 'GutenKit' or 'Wpmet GutenKit' in the installed plugins listAffected if GutenKit plugin appears in the plugins list
-
Check installed version numberIn Plugins section, click on GutenKit details or view the plugin file header to find the current version numberAffected if Version number is lower than 2.2.3 (for example 2.2.2, 2.2.1, 2.2.0, etc.)
-
Confirm plugin is activeIn WordPress admin > Plugins, verify that GutenKit shows as 'Active' rather than 'Inactive'Affected if Plugin is active and version is below 2.2.3
-
Review recent database content for suspicious scriptsInspect postmeta, options, or custom tables where GutenKit stores user-submitted content, looking for script tags, javascript: URIs, or event handler attributes in stored dataAffected if Unexpected JavaScript code or HTML script tags found in database fields associated with GutenKit
Environment is affected if GutenKit plugin version is below 2.2.3 and the plugin is active, allowing stored XSS payloads to execute when content is viewed by other users.
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 · scoped2.2.3
Update GutenKit plugin to the latest version which includes proper input sanitization and output encoding to prevent XSS attacks.
2.2.3
- Backup the WordPress site before performing any updates
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the GutenKit plugin in the list
- Click 'Update now' or navigate to the plugin page to update to version 2.2.3
- Verify the plugin version shows 2.2.3 or higher after updating
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Gutenkit
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46253 — 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-46253 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