Cyber Resilience

CVE-2026-1978

Kalyan02 Nanocms ≤ 0.4

Published
06 February 2026
Modified
27 February 2026
Patch / advisory
View advisory
CVSS Score v4 5.5
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0036 29th percentile
Risk Priority 38 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-1978 is a medium-severity Forced Browsing (CWE-425) vulnerability in Kalyan02 Nanocms. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-1978 is a vulnerability in kalyan02 NanoCMS versions up to 0.4, published on 2026-02-06. It affects an unknown functionality within the /data/pagesdata.txt file of the User Information Handler component, enabling direct request manipulation.

The vulnerability is remotely exploitable by unauthenticated attackers requiring low attack complexity and no user interaction. Exploitation allows limited disclosure of confidential information, with no impact on integrity or availability, as reflected in its CVSS v3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N). It maps to CWE-425 (Direct Request).

Advisories recommend changing configuration settings to mitigate the issue. The exploit is publicly available, with references including the NanoCMS GitHub repository at https://github.com/kalyan02/NanoCMS/ and the vulnerable file at https://github.com/kalyan02/NanoCMS/blob/master/data/pagesdata.txt, along with VulDB entries at https://vuldb.com/?ctiid.344500, https://vuldb.com/?id.344500, and https://vuldb.com/?submit.743260.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

A vulnerability was detected in kalyan02 NanoCMS up to 0.4. Affected by this issue is some unknown functionality of the file /data/pagesdata.txt of the component User Information Handler. Performing a manipulation results in direct request. It is possible to initiate…

more

the attack remotely. The exploit is now public and may be used. You should change the configuration settings.

CWE(s)
CWE-425

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-65011Shared CWE-425
CVE-2025-10287Shared CWE-425
CVE-2025-57823Shared CWE-425
CVE-2026-8205Shared CWE-425
CVE-2023-1682Shared CWE-425
CVE-2026-7500Shared CWE-425
CVE-2025-67844Shared CWE-425
CVE-2024-33897Shared CWE-425
CVE-2025-26381Shared CWE-425
CVE-2024-7153Shared CWE-425

Affected Assets

kalyan02
nanocms
≤ 0.4

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

AC-3 directly requires enforcement of authorizations for access to resources such as URLs, scripts, and files, structurally preventing forced browsing.

AC-24 Access Control Decisions good match

AC-24 requires that access-control decisions be applied to every request, addressing the missing enforcement on restricted URLs.

AC-6 Least Privilege partial match

AC-6 requires restricting authorizations to the minimum needed, reducing the set of resources that must be protected against direct requests.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
prevents

Directly requires policy-driven definition, enforcement, and review of authorizations on resources such as URLs.

PR.IR-01 mostly match
prevents

Protects environments from unauthorized logical access, which includes preventing direct requests to restricted paths.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect forced-browsing flaws, but the control itself does not prevent them in production.

A.8.3 Information access restriction mostly match
prevents

Information access restriction implements the technical enforcement that directly blocks unauthorized direct requests.

A.5.15 Access control partial match
prevents

Access control policy directly requires authorization checks on all resources, preventing forced browsing.

A.5.18 Access rights partial match
degrades

Managing access rights ensures every URL/script/file is explicitly authorized, mitigating direct request attacks.

A.8.2 Privileged access rights partial match
degrades

Privileged access rights control enforces least-privilege checks on restricted endpoints.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC can include authorization design, yet the control itself does not guarantee runtime enforcement.

References