CVE-2025-70890VulnerabilityPublished 15 Jan 2026

CVE-2025-70890: Cyber-Cafe-Management-System-CVEs · n/a

Affects Cyber-Cafe-Management-System-CVEsSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.1Medium

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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 impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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 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
GitHubefekaanakkar/Cyber-Cafe-Management-System-CVEs`pkg:github/efekaanakkar/Cyber-Cafe-Management-System-CVEs`Other threats	Affected =1.0	Fixed in–

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

AI-suggested

To mitigate CVE-2025-70890, organizations should implement strict input validation and sanitization on all user-supplied data, especially the username parameter in add-users.php. Employing output encoding techniques to neutralize scripts before rendering user input in the browser is essential. Limit user privileges to the minimum necessary to reduce the risk posed by authenticated attackers. Conduct regular security audits and penetration testing focused on XSS vulnerabilities. Educate users and administrators about the risks of stored XSS and encourage cautious behavior when interacting with user-generated content. Monitor logs for suspicious activity related to user creation or modification. If feasible, isolate the Cyber Cafe Management System from critical internal networks to contain potential exploitation. Finally, maintain awareness of vendor updates or patches and apply them promptly once released.

Description

CVE-2025-70890 is a stored cross-site scripting (XSS) vulnerability in Cyber Cafe Management System v1.0. An authenticated attacker can inject malicious JavaScript code into the username parameter via the add-users.php endpoint. This injected code is stored on the server and executed in the browsers of users who access the affected page, potentially leading to session hijacking or other malicious actions. The vulnerability requires authentication but no special privileges and user interaction is needed to trigger the payload. The CVSS score is 6.1, indicating a medium severity. There are no known exploits in the wild and no patches currently available. European organizations using this system should be cautious, especially those in countries with higher adoption of cyber cafe management solutions.

Impact

For European organizations, this vulnerability poses a risk primarily to entities using the Cyber Cafe Management System v1.0, which may include internet cafes, small business environments, or public access points. Exploitation could lead to session hijacking, credential theft, or unauthorized actions performed under the guise of legitimate users, potentially compromising confidentiality and integrity of user data. Although availability impact is low, the breach of trust and data confidentiality can have regulatory implications under GDPR, especially if personal data is exposed or manipulated. The requirement for authentication limits the attack surface but does not eliminate risk, as insider threats or compromised accounts could be leveraged. Organizations relying on this system for user management or access control should be aware that attackers could escalate privileges or pivot to other internal systems if the vulnerability is exploited. The lack of patches increases the urgency for mitigating controls. The impact is more pronounced in countries with higher deployment of cyber cafe management solutions or where such cafes serve as critical internet access points, potentially affecting a wide user base including tourists and local populations.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Jan 2026, 21:36 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats