LiveActive security incident?Get immediate response
CVE Record

CVE-2023-28620: WordPress Cyberus Key Plugin <= 1.0 is vulnerable to Cross Site Scripting (XSS)

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Cyberus Labs Cyberus Key plugin <= 1.0 versions.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a stored cross-site scripting issue in the WordPress Cyberus Key plugin up to version 1.0. An administrator-level user could store script content that later runs when another user views it. Business risk is limited by high required privileges, but compromised admin accounts could turn it into a broader site and user-trust issue.

Executive priority

Handle as a moderate-priority WordPress hygiene issue. It is not shown as actively exploited, and it needs admin-level access, but it can increase impact after admin compromise. Prioritize public sites, regulated environments, and sites with many administrators.

Technical view

CVE-2023-28620 is CWE-79 stored XSS in Cyberus Labs Cyberus Key for WordPress <= 1.0. CVSS 3.1 is 5.9 with network access, low complexity, high privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact. Sources do not identify the vulnerable field or a fixed version.

Likely exposure

Exposure appears limited to WordPress sites with the Cyberus Labs Cyberus Key plugin installed at version 1.0 or earlier. The source bundle provides no CPEs and no broader affected product list, so asset validation should focus on plugin inventory rather than assumptions.

Exploitation context

The provided data does not show CISA KEV listing or active exploitation. Exploitation requires administrator-level access and user interaction, which lowers opportunistic risk. Stored XSS still matters if an admin account is compromised or misused, because malicious content can persist and execute for later viewers.

Researcher notes

Public details are sparse. The record confirms authenticated admin-plus stored XSS and CVSS vector, but not the affected code path, sink, payload context, or fixed release. Avoid assuming exploitability beyond the stated privilege and interaction requirements.

Mitigation direction

  • Check Cyberus Labs and Patchstack guidance for an official fixed version or workaround.
  • Disable or remove Cyberus Key where it is not required.
  • Restrict WordPress administrator access to trusted accounts only.
  • Review administrator accounts and revoke stale or unnecessary privileges.
  • Prioritize remediation on public or high-trust WordPress sites.

Validation and detection

  • Inventory WordPress sites for the cyberus-key plugin.
  • Confirm whether installed versions are 1.0 or earlier.
  • Check whether the plugin is active on production sites.
  • Review admin user activity around plugin configuration changes.
  • Document compensating controls if no vendor fix is available.
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-2023-28620 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
5.9 (3.1)
Known Exploited
No
Published

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

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
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L1.73.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2023-28620Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
Cyberus LabsCyberus Keycyberus-key, 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.