LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22487: WordPress Speed Kit plugin <= 2.0.2 - Broken Access Control vulnerability

Missing Authorization vulnerability in baqend Speed Kit baqend allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Speed Kit: from n/a through <= 2.0.2.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22487 affects the WordPress Speed Kit plugin by baqend through version 2.0.2. A logged-in user may be able to perform actions they should not be authorized to perform. The reported impact is limited to integrity, with no stated confidentiality or availability impact.

Executive priority

Treat this as a moderate-priority WordPress hygiene issue. It does not currently show public evidence of active exploitation, but it can affect site integrity where authenticated users exist. Prioritize externally reachable WordPress sites with multiple contributors, customers, or low-trust accounts.

Technical view

The issue is a missing authorization flaw, mapped to CWE-862, in Speed Kit <= 2.0.2. CVSS 3.1 is 4.3: network-accessible, low complexity, privileges required, no user interaction, unchanged scope, low integrity impact only. Public sources do not identify the vulnerable function, endpoint, or fixed version.

Likely exposure

Exposure is most relevant to WordPress sites running the Speed Kit plugin at version 2.0.2 or earlier, especially where untrusted or lower-privileged users can authenticate. Sites without the plugin, or running versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. The CVSS vector indicates an attacker needs valid privileges, so risk depends on who can log in to the WordPress site and what unauthorized action is possible.

Researcher notes

Public detail is limited. The sources identify missing authorization but do not name the affected route, capability check, exploit method, or fixed version. The CVE metadata description says <=2.0.2, while the affected version field is sparse, so validate against vendor and Patchstack updates.

Mitigation direction

  • Inventory WordPress sites for the Speed Kit plugin and record installed versions.
  • Check baqend, WordPress plugin, and Patchstack guidance for a fixed release or official mitigation.
  • Update the plugin if an official fixed version is available.
  • Disable or remove the plugin where it is unnecessary or cannot be safely validated.
  • Limit WordPress accounts to users who require access and appropriate roles.

Validation and detection

  • Confirm whether Speed Kit is installed on each WordPress site.
  • Verify whether the installed version is 2.0.2 or earlier.
  • Review WordPress user roles for unnecessary authenticated access.
  • Check vendor or Patchstack advisories for fixed-version guidance.
  • Monitor site administration logs for unexpected changes by lower-privileged users.
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-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-2026-22487 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-22487Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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
baqendSpeed Kitbaqend, 0unaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.