VulnerabilityPublished 6 Feb 2026Updated 23 Feb 2026

CVE-2026-1978: kalyan02 NanoCMS · Direct Request

Affects kalyan02 NanoCMSSource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS: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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
kalyan02NanoCMS	Affected 0.1 – 0.4 4 affected builds	Fixed in–
GitHubkalyan02/NanoCMS`pkg:github/kalyan02/NanoCMS`Other threats	Affected 0.1 – 0.4 4 affected builds	Fixed in–

CPE configurations (1)

cpe:2.3:a:kalyan02:nanocms:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediately review and modify the configuration settings of NanoCMS, focusing on access controls and validation mechanisms related to the /data/pagesdata.txt file to prevent unauthorized direct requests.
Implement strict input validation and sanitization on all requests targeting user information handlers to block malformed or malicious requests.
Restrict network access to the CMS backend and sensitive files using firewalls or web application firewalls (WAFs) to limit exposure to trusted IPs or internal networks.
Monitor access logs for unusual or repeated requests to /data/pagesdata.txt or related endpoints, enabling early detection of exploitation attempts.
If possible, isolate the CMS environment or run it with least privilege to minimize the impact of a successful exploit.
Engage with the vendor or community to obtain patches or updates as they become available, and plan for timely deployment.
Conduct regular security assessments and penetration tests focusing on CMS components to identify and remediate similar vulnerabilities proactively.
Educate administrators and developers on secure configuration practices for NanoCMS and similar CMS platforms to prevent misconfigurations that facilitate exploitation.

Description

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 the attack remotely. The exploit is now public and may be used. You should change the configuration settings.

Impact

The primary impact of CVE-2026-1978 is unauthorized access or manipulation of user information managed by the NanoCMS system. This can lead to confidentiality breaches where sensitive user data or content is exposed to attackers. Integrity of the CMS content could also be compromised if attackers modify page data, potentially damaging organizational reputation or misleading users. Availability impact is minimal as the vulnerability does not indicate denial-of-service capabilities. Since the exploit requires no authentication or user interaction, attackers can remotely target vulnerable systems at scale, increasing the risk for organizations with public-facing NanoCMS deployments. Organizations relying on NanoCMS for critical web content or user management may face operational disruptions or compliance issues if sensitive data is exposed. The public availability of the exploit increases the likelihood of opportunistic attacks, especially against unpatched or misconfigured systems. However, the overall impact is somewhat limited by the niche use of NanoCMS and the partial confidentiality impact indicated by the CVSS score.

References

Community reviews

Loading reviews…