dbcve.org
LearnhouseApplication

CVE-2025-12268

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to after 2025-09-21 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in LearnHouse up to 98dfad76aad70711a8113f6c1fdabfccf10509ca. Impacted is an unknown function of the file /api/v1/courses/ of the component Course Thumbnail Handler. The manipulation of the argument thumbnail leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unrestricted file upload vulnerability in LearnHouse's Course Thumbnail Handler at /api/v1/courses/. The thumbnail argument lacks proper file type validation and storage restrictions, allowing attackers to upload malicious files (e.g., web shells) that could enable remote code execution.

MitigationImplement strict allowlist-based file type validation, enforce file size limits, store uploads outside webroot, rename files to prevent executable extensions, and disable script execution in the upload directory. Consider placing a WAF or API gateway in front as a temporary compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LearnhouseApplication
Affected:<= 2025-09-21

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify LearnHouse installation and version
    Locate the LearnHouse application files and check the version metadata (e.g., package.json, setup.py, or version file in the installation directory)
    Affected if The installed version is Learnhouse Learnhouse and is at or before the 2025-09-21 release date
  2. Confirm /api/v1/courses/ endpoint is exposed
    Check if the LearnHouse web application has the /api/v1/courses/ endpoint available and accessible from the network
    Affected if The endpoint is reachable and accepts requests (even if authentication is required, the endpoint exists)
  3. Inspect thumbnail upload configuration
    Examine the backend code or configuration for the /api/v1/courses/ endpoint, specifically how the thumbnail parameter is handled in the upload logic
    Affected if The thumbnail parameter accepts file uploads without strict file type validation or uses only client-side validation
  4. Verify upload directory location
    Check the application configuration or upload handler code to determine where uploaded thumbnail files are stored
    Affected if Uploaded files are stored within the web server's document root or a publicly accessible directory
  5. Check file type validation implementation
    Review the upload handling code for the thumbnail parameter to see if it implements server-side allowlist validation of file content or magic bytes
    Affected if There is no server-side allowlist validation, or only filename extension-based validation is used without content inspection

A user is affected if they are running any Learnhouse version dated 2025-09-21 or earlier with the /api/v1/courses/ endpoint exposed and the thumbnail upload feature enabled without strict server-side file type validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2025-09-21
Interim mitigation

Implement strict allowlist-based file type validation, enforce file size limits, store uploads outside webroot, rename files to prevent executable extensions, and disable script execution in the upload directory. Consider placing a WAF or API gateway in front as a temporary compensating control.

Fix this in Learnhouse Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12268 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12268 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data