CVE-2025-12269VulnerabilityPublished 27 Oct 2025

CVE-2025-12269: LearnHouse · Cross Site Scripting

Affects LearnHouseSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system 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 to 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 27 Oct 2025
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

AI-suggested

1. Implement strict Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. 2. Employ web application firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the vulnerable endpoint. 3. Conduct user awareness training focused on recognizing phishing attempts and suspicious links to reduce the likelihood of user interaction with malicious content. 4. Monitor application logs and network traffic for unusual activities related to /dash/org/settings/previews or other suspicious requests. 5. If possible, apply input validation and output encoding at the application layer as an interim fix, especially for the affected component, even if official patches are unavailable. 6. Segment and isolate LearnHouse deployments within the network to limit lateral movement in case of compromise. 7. Engage with the vendor persistently for patch release or consider alternative platforms if the risk is unacceptable. 8. Regularly update and patch all other components and dependencies to minimize overall attack surface.

Description

A vulnerability was found in LearnHouse up to 98dfad76aad70711a8113f6c1fdabfccf10509ca. The affected element is an unknown function of the file /dash/org/settings/previews of the component Account Setting Page. The manipulation results in cross site scripting. It is possible to launch the attack remotely. The exploit has been made public and could be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the impact of CVE-2025-12269 can be significant, especially for those relying on LearnHouse for educational or organizational management purposes. Successful exploitation could lead to theft of sensitive user credentials, unauthorized access to user accounts, and potential compromise of organizational data. This could result in reputational damage, regulatory non-compliance (e.g., GDPR violations due to data breaches), and operational disruptions. Since the vulnerability requires user interaction, phishing or social engineering campaigns could be used to trigger exploitation, increasing the attack surface. The lack of vendor response and patches means organizations must rely on internal controls and compensating measures to protect their environments. The rolling release model complicates tracking vulnerable versions, potentially delaying mitigation efforts. Overall, the vulnerability poses a moderate risk but could escalate if exploited in targeted attacks against European institutions using LearnHouse.

Summary

CVE-2025-12269 is a cross-site scripting (XSS) vulnerability identified in the LearnHouse platform, affecting the Account Setting Page component located at /dash/org/settings/previews. The vulnerability arises from improper sanitization or validation of user-supplied input in an unknown function within this component, allowing an attacker to inject malicious scripts that execute in the context of the victim's browser. This flaw can be exploited remotely without authentication, though it requires user interaction, such as clicking a crafted link or visiting a malicious page. The CVSS 4.0 vector indicates low attack complexity and no privileges required, but user interaction is necessary. The impact primarily affects confidentiality and integrity by enabling session hijacking, credential theft, or unauthorized actions performed on behalf of the user. Although no active exploits have been observed in the wild, the public availability of exploit code increases the risk of exploitation. Organizations using LearnHouse should be aware of this vulnerability and take proactive steps to mitigate potential attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2025, 12:24 UTC

Technical details

References

Community reviews

Related threats