Kb SupportWordPress extension · Wpchill
CVE-2022-27852
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 · uneditedMultiple Unauthenticated Stored Cross-Site Scripting (XSS) vulnerabilities in KB Support (WordPress plugin) <= 1.5.5 versions.
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 confidenceMultiple unauthenticated stored XSS vulnerabilities exist in KB Support WordPress plugin versions 1.5.5 and below. Attackers can inject malicious JavaScript into plugin fields that are stored in the database and executed when other users view the affected content, potentially compromising administrator sessions or defacing the site.
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
Kb SupportWordPress extension
<= 1.5.5CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check KB Support plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate KB Support. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header or readme.txt for the Version field.Affected if The installed version is 1.5.5 or lower.
-
Verify plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm KB Support shows as 'Active' under the plugin status.Affected if The plugin is active and the version is 1.5.5 or below.
-
Check for unauthenticated submission capabilityThe vulnerability is unauthenticated stored XSS - meaning malicious scripts can be injected without logging in. Review any public-facing forms or submission endpoints provided by the plugin (such as ticket submission forms).Affected if The plugin has public-facing input forms and the version is 1.5.5 or below.
-
Inspect database for suspicious stored contentQuery the WordPress database tables where KB Support stores user submissions (typically wp_posts, wp_postmeta, or custom tables created by the plugin). Look for unexpected script tags, iframe tags, or javascript: URIs in content fields.Affected if Malicious JavaScript code is found stored in plugin-related database records.
A site is affected if the KB Support plugin version is 1.5.5 or lower and the plugin is active, as this enables unauthenticated attackers to inject and store 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.
From vendor dataUpdate KB Support plugin to a version newer than 1.5.5. If no patched version is available, remove the plugin until a fix is released.
Fix this in Kb Support
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27852 — 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-2022-27852 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