LiveActive security incident?Get immediate response
CVE Record

CVE-2022-27852: WordPress KB Support plugin <= 1.5.5 - Multiple Unauth. Stored Cross-Site Scripting (XSS) vulnerabilities

Multiple Unauthenticated Stored Cross-Site Scripting (XSS) vulnerabilities in KB Support (WordPress plugin) <= 1.5.5 versions.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

KB Support, a WordPress help desk plugin, had multiple stored XSS flaws in versions up to 1.5.5. An unauthenticated attacker could potentially store malicious script content that runs when another user views it. This is not described as destructive, but it can affect confidentiality and integrity of WordPress sessions or page content.

Executive priority

Handle as a moderate web-application risk. It should be prioritized for public WordPress support portals and sites with privileged staff reviewing user-submitted tickets, but the provided sources do not support emergency active-exploitation claims.

Technical view

CVE-2022-27852 is CWE-79 stored cross-site scripting in KB Support <= 1.5.5. The CVSS 3.1 score is 6.1: network exploitable, low complexity, no privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is most likely on WordPress sites that installed the KB Support plugin package and still run version 1.5.5 or earlier, especially where support-ticket or help-desk submission features are reachable by unauthenticated users.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The issue is stored XSS, so practical impact depends on whether attacker-supplied content can be saved and later viewed by an administrator or other user.

Researcher notes

Evidence is limited to the CVE and Patchstack vulnerability record summarized in the bundle. The bundle does not provide payload details, fixed-version data, or exploitation telemetry, so validation should focus on inventory, version confirmation, and vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the KB Support plugin and installed version.
  • Check WPChill or Patchstack guidance for the current fixed or recommended release.
  • If guidance is unavailable, consider disabling KB Support where business impact allows.
  • Restrict unauthenticated support submissions if that does not break required workflows.
  • Monitor WordPress admin activity for unexpected account, content, or plugin changes.

Validation and detection

  • Confirm whether KB Support is installed on each WordPress instance.
  • Record plugin versions and flag any version 1.5.5 or earlier.
  • Review exposed support or ticket forms that accept unauthenticated input.
  • Inspect stored ticket content for unexpected script-like markup or suspicious links.
  • Verify remediation against vendor or Patchstack guidance before closing the finding.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-27852 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2022-27852Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WPChill Media Labs L.L.CKB Supportkb-support, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.