CVE-2026-71801

Hardcoded Default Token Secret Enables Remote Authentication Bypass in s‑pms SPMS

Published Sep 9, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
An issue was discovered in s-pms SPMS-Server through v1.0. The application contains a hardcoded default access token secret within its core configuration file, which is not overridden or removed in the production environment profile. A remote, unauthenticated attacker can locally forge valid administrative session tokens to completely bypass the authentication mechanism gaining full unauthorized access to protected backend APIs.

Analysis

AI-generated

Technical impact

An attacker can bypass authentication by forging administrative session tokens because the application stores a hardcoded default access token secret in its core configuration and never replaces it when running in the production profile. The vulnerability allows the attacker to generate a valid token without any credentials, giving unrestricted access to the protected backend APIs.

Affected Systems

Affected systems are installations of the s‑pms SPMS 1.0. No vendor or product names beyond the application identifier are listed, so any environment running this version with the default configuration is potentially impacted.

Risk and Exploitability

Because the exploit requires only the knowledge of the hardcoded secret, it can be carried out remotely and without user interaction, making it both high‑impact and high‑availability. While the EPSS score indicates a low probability of exploitation (< 1%) and the issue is not listed in the CISA KEV catalog, the CVSS score of 9.8 indicates high severity due to unauthenticated remote authentication bypass. The attacker can freely perform any operation that an administrator can, potentially leading to data exfiltration, configuration changes, or system takeover.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Remove the hardcoded default access token secret from the production configuration and initialize the token secret with a securely generated random value.
  • Invalidate all existing tokens, including those generated with the default secret, and force a re‑authentication for all administrators.
  • Implement additional safeguards such as multi‑factor authentication for administrative API endpoints and ensure that token generation never uses a static secret.

Generated by OpenCVE AI on September 21, 2026 at 06:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
Title Hardcoded Default Token Secret Enables Remote Authentication Bypass in s‑pms SPMS
Type Values Removed Values Added
Title Hardcoded Access Token Secret Allows Authentication Bypass in SPMS-Server
Weaknesses CWE-259
CWE-287
Type Values Removed Values Added
Weaknesses CWE-798
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Hardcoded Access Token Secret Allows Authentication Bypass in SPMS-Server
Weaknesses CWE-259
CWE-287
Type Values Removed Values Added
Description An issue was discovered in s-pms SPMS-Server through v1.0. The application contains a hardcoded default access token secret within its core configuration file, which is not overridden or removed in the production environment profile. A remote, unauthenticated attacker can locally forge valid administrative session tokens to completely bypass the authentication mechanism gaining full unauthorized access to protected backend APIs.
References

Subscriptions

No data.

Weaknesses
  • CWE-798

    Use of Hard-coded Credentials

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Sep 14, 2026, 12:26 PM
Reserved
Aug 7, 2026, 12:00 AM
Status
Deferred
Published
Sep 9, 2026, 9:17 PM
Modified
Sep 14, 2026, 1:18 PM