LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22205: SPIP < 4.4.10 Authentication Bypass via PHP Type Juggling

SPIP versions prior to 4.4.10 contain an authentication bypass vulnerability caused by PHP type juggling that allows unauthenticated attackers to access protected information. Attackers can exploit loose type comparisons in authentication logic to bypass login verification and retrieve sensitive internal data.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

SPIP versions before 4.4.10 are reported vulnerable to an authentication bypass. An unauthenticated attacker may access protected information by abusing weak PHP comparison behavior. This is a high-priority issue for organizations running SPIP, especially internet-facing sites.

Executive priority

Treat this as a near-term remediation item. It can expose protected information without credentials, but the provided sources do not confirm active exploitation. Prioritize public SPIP sites and systems holding sensitive internal content.

Technical view

CVE-2026-22205 is a CWE-288 authentication bypass in SPIP prior to 4.4.10. The source bundle attributes it to PHP type juggling in authentication logic, enabling unauthenticated access to sensitive internal data. CVSS 4.0 score is 8.7, with network attack vector, low complexity, no privileges, and no user interaction.

Likely exposure

Exposure is likely limited to organizations running SPIP versions prior to 4.4.10. Publicly reachable SPIP instances carry the highest business risk because exploitation requires network access and no authentication.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation for CVE-2026-22205. The flaw is still serious because the described attack path is unauthenticated, low complexity, and targets confidentiality.

Researcher notes

The source bundle contains a clear pre-4.4.10 statement, but the affected-products metadata is sparse and internally limited. Validate against the CVE record and vendor advisory before broad scoping. Do not assume impact beyond SPIP based on the provided evidence.

Mitigation direction

  • Upgrade SPIP to version 4.4.10 or later per the vendor advisory.
  • Inventory all SPIP deployments, including externally hosted or agency-managed sites.
  • If immediate upgrade is not possible, check SPIP vendor guidance for supported temporary controls.
  • Prioritize internet-facing SPIP instances for remediation first.

Validation and detection

  • Confirm whether SPIP is deployed in your environment.
  • Record the installed SPIP version for each instance.
  • Verify remediated systems run SPIP 4.4.10 or later.
  • Review vendor advisory details for any additional validation guidance.
  • Check access logs for unusual unauthenticated requests to protected areas.
Prepared
Confidence
medium
Sources
5

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 · low confidence lookup

CWE-288: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22205 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
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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
4Source 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
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-22205Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SPIPSPIP0unaffected
Weakness

CWE details

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

CWE-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.