CVE-2025-12270VulnerabilityPublished 27 Oct 2025

CVE-2025-12270: LearnHouse · Improper Control of Resource Identifiers

Affects LearnHouseSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% 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: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: Low
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: 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: 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 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 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 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 validation and sanitization of all resource identifiers in API requests to prevent unauthorized manipulation. 2. Enforce robust authentication and authorization mechanisms on the affected API endpoints, ensuring only legitimate users can access or modify assignment resources. 3. Apply network-level access controls such as IP whitelisting and API gateways to restrict access to the submission handler endpoints. 4. Monitor API usage logs for anomalous patterns indicative of exploitation attempts, including unusual resource identifier values or access frequencies. 5. Engage with the vendor or community to obtain patches or updates as they become available, despite the current lack of response. 6. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious API requests targeting resource identifiers. 7. Educate development and security teams about secure API design principles to prevent similar vulnerabilities in continuous delivery environments. 8. Conduct regular security assessments and penetration testing focused on API endpoints handling sensitive educational data.

Description

A vulnerability was determined in LearnHouse up to 98dfad76aad70711a8113f6c1fdabfccf10509ca. The impacted element is an unknown function of the file /api/v1/assignments/{assignment_id}/tasks/{task_id}/sub_file of the component Student Assignment Submission Handler. This manipulation causes improper control of resource identifiers. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, particularly educational institutions and e-learning service providers using LearnHouse, this vulnerability poses a risk of unauthorized access or manipulation of student assignment data. Confidentiality could be compromised if attackers access sensitive student submissions or grading information. Integrity may be affected if attackers alter assignment data, potentially impacting academic records and evaluation processes. Availability impact is minimal as the vulnerability does not directly enable denial-of-service conditions. The ease of remote exploitation without authentication increases the threat level, especially in environments with exposed API endpoints. This could lead to reputational damage, regulatory non-compliance (e.g., GDPR breaches due to unauthorized data access), and operational disruptions in academic workflows. Organizations relying on LearnHouse should prioritize detection and mitigation to prevent exploitation.

Summary

CVE-2025-12270 identifies a vulnerability in LearnHouse, an educational platform, specifically within the Student Assignment Submission Handler component. The flaw exists in an API endpoint at /api/v1/assignments/{assignment_id}/tasks/{task_id}/sub_file, where improper control of resource identifiers allows attackers to manipulate these identifiers remotely. This manipulation could lead to unauthorized access or modification of assignment-related resources. The vulnerability does not require user interaction or authentication, increasing its risk profile. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P) indicates network attack vector, low attack complexity, no privileges or user interaction needed, and partial impact on confidentiality. The vendor uses continuous delivery with rolling releases, complicating version tracking and patch availability. Despite early vendor notification, no response or patch has been provided, and no public exploits have been observed yet. This vulnerability could be leveraged to access or alter student assignment data, potentially impacting data integrity and confidentiality within educational institutions using LearnHouse.

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