CVE-2025-55006
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 · uneditedFrappe Learning is a learning system that helps users structure their content. In versions 2.33.0 and below, the image upload functionality did not adequately sanitize uploaded SVG files. This allowed users to upload SVG files containing embedded JavaScript or other potentially malicious content. Malicious SVG files could be used to execute arbitrary scripts in the context of other users. A fix for this issue is planned for version 2.34.0.
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 confidenceFrappe Learning versions 2.33.0 and below have a stored XSS vulnerability in the image upload functionality. The application fails to sanitize SVG files during upload, allowing attackers to embed malicious JavaScript within SVG content. When other users view the uploaded SVG, the embedded script executes in their browser context.
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>= 2.0.0, < 2.34.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Frappe Learning is installedCheck your system's installed packages or application list for 'frappe-learning', 'education', or related Frappe apps. Look in your Frappe bench apps folder or pip packages.Affected if Frappe Learning is present on the system
-
Determine the installed version of Frappe LearningRun 'bench apps' to list installed apps and their versions, or check the app's hooks.py file for the version number. Compare against the affected range: >= 2.0.0 and < 2.34.0.Affected if The installed version falls within 2.0.0 through 2.33.x inclusive
-
Check if file upload functionality exists in the learning moduleNavigate to the Learning module in Frappe and look for document types that accept file attachments, particularly those that may accept image uploads such as Course, Program, Article, or Topic doctypes.Affected if The learning module allows users to upload or attach files to any doctype
-
Verify if SVG file uploads are permittedAttempt to upload a test SVG file through the Learning module's document creation or edit interface, or inspect the allowed file extensions in the relevant File or Attachment doctype configurations.Affected if SVG files can be uploaded without restriction or validation
-
Confirm whether uploaded files are publicly accessible or viewable by other usersCheck the file sharing permissions and web templates in the Learning module to see if uploaded files are served to other users or displayed in the learning portal.Affected if Uploaded files are accessible to other users or displayed in the learning portal interface
Your environment is affected if Frappe Learning version 2.0.0 through 2.33.x is installed AND the Learning module allows users to upload files that can be viewed or accessed by other users, enabling stored XSS via malicious SVG content.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped2.34.0
Restrict or block SVG file uploads until version 2.34.0 is available. Implement server-side SVG sanitization using a library like DOMPurify or bleach to strip executable content from SVG files before storage.
2.34.0
- 1. Back up your current site database and files before upgrading
- 2. Update the Frappe Learning app by running the bench update command (e.g., `bench update --apps frappe learning`) or by pulling the latest version of the learning app
- 3. Verify the upgrade completed successfully by checking the installed version
- 4. Restart the relevant services (Frappe bench, web server) to ensure the new version is fully active
- 5. Test the image upload functionality to confirm SVG files are now properly sanitized
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-55006 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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