CVE-2025-70960VulnerabilityPublished 2 Feb 2026Updated 3 Feb 2026

CVE-2025-70960: n/a

Source CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.4Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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 2 Feb 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-25.

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

AI-suggested

To mitigate CVE-2025-70960, organizations should first verify if they are running Tendenci CMS version 15.3.7 or earlier and plan to upgrade to a patched version once available. In the absence of an official patch, implement strict input validation on all user-submitted content in the Forums module, ensuring that scripts and HTML tags are either sanitized or escaped. Employ output encoding techniques to neutralize any injected scripts before rendering content in users' browsers. Restrict forum posting privileges to trusted users and monitor forum content regularly for suspicious or anomalous entries. Deploy Content Security Policy (CSP) headers to limit the execution of unauthorized scripts and reduce the impact of potential XSS payloads. Additionally, educate users about the risks of clicking on suspicious links or interacting with unexpected forum content. Logging and alerting on unusual forum activity can help detect exploitation attempts early. Finally, consider isolating the forum environment or using web application firewalls (WAFs) with XSS detection rules as an additional layer of defense.

Description

CVE-2025-70960 is a stored cross-site scripting (XSS) vulnerability found in the Forums module of Tendenci CMS version 15.3.7. This vulnerability allows an attacker with limited privileges to inject malicious scripts or HTML payloads that are permanently stored and executed when other users view the affected forum content. Exploitation requires user interaction and some level of authentication, but no complex attack conditions. The vulnerability impacts confidentiality and integrity by enabling script execution in the context of other users, potentially leading to session hijacking or data manipulation. Although no known public exploits exist yet, organizations using Tendenci CMS should prioritize patching or mitigating this issue. European organizations using this CMS, especially those with active community forums, are at risk. Countries with higher Tendenci CMS adoption or strategic interest in community-driven platforms are more likely to be affected. Mitigation includes applying input validation and output encoding, restricting user privileges, and monitoring forum content for suspicious entries.

Impact

For European organizations using Tendenci CMS, particularly those operating community forums or membership sites, this vulnerability poses a risk to user data confidentiality and trust. Attackers could exploit the stored XSS to hijack user sessions, steal sensitive information, or conduct phishing attacks by injecting deceptive content. This can lead to reputational damage, loss of user confidence, and potential regulatory consequences under GDPR if personal data is compromised. Since the vulnerability requires some level of authentication and user interaction, internal users or registered members could be targeted to escalate privileges or spread malicious payloads. The persistent nature of stored XSS means that once injected, the malicious code remains active until removed, increasing the window of exposure. Although availability is not impacted, the integrity and confidentiality risks are significant enough to warrant immediate attention. Organizations relying on Tendenci CMS for critical communications or community engagement should consider this vulnerability a moderate threat that could facilitate broader attacks if chained with other vulnerabilities.

Summary

CVE-2025-70960 identifies a stored cross-site scripting (XSS) vulnerability in the Forums module of Tendenci CMS version 15.3.7. Stored XSS occurs when malicious scripts injected by an attacker are permanently saved on the target server and executed in the browsers of users who access the infected content. In this case, the vulnerability allows an attacker with at least limited privileges (PR:L) to inject crafted HTML or JavaScript payloads into forum posts or threads. When other users view these posts, the malicious code executes within their browser context, potentially allowing the attacker to steal session cookies, perform actions on behalf of the victim, or manipulate displayed content. The CVSS vector indicates the attack can be performed remotely (AV:N) with low attack complexity (AC:L), requiring some privileges and user interaction (UI:R). The scope is changed (S:C), meaning the vulnerability affects resources beyond the initially vulnerable component. Confidentiality and integrity impacts are low (C:L, I:L), while availability is not affected (A:N). No patches or known exploits are currently reported, but the vulnerability is publicly disclosed and should be addressed promptly. The root cause is improper input sanitization and output encoding in the Forums module, a common weakness classified under CWE-79. This vulnerability highlights the importance of secure coding practices in web applications, especially those handling user-generated content.

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

github.com/emirhanyucelll/tendenci/blob/main/Readme.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 10 Feb 2026, 11:13 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats