CVE-2025-48884
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 · uneditedGalette is a membership management web application for non profit organizations. In versions 1.1.5.2 and below, Galette's Document Type is vulnerable to Cross-site Scripting. This issue is fixed in version 1.2.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 · moderate confidenceGalette versions 1.1.5.2 and below contain a stored Cross-site Scripting (XSS) vulnerability in the Document Type feature. An attacker with the ability to create or modify document types can inject malicious JavaScript code that will execute in the browsers of other users viewing those documents.
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< 1.2.0= 1.2.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Check installed Galette versionLocate the version file or check the version displayed in the admin dashboard footer or about page. Common locations include a VERSION file in the root directory or a config file that stores application metadata.Affected if The installed version is 1.1.5.2 or below, or if it is exactly 1.2.0
-
Verify Document Type feature is in useNavigate to the Document Type management section in the Galette admin interface, typically found under Configuration or Parameters menus. Check if any document types have been created.Affected if Document Types exist in the system, making the XSS vector available
-
Inspect document type entries for suspicious contentAccess the database table storing document types (commonly named galette_document_types or similar) or view them through the admin interface. Look for any entries containing HTML tags, script elements, or JavaScript event handlers in the type name or description fields.Affected if Any document type entry contains unencoded HTML, script tags, or javascript: URIs
-
Check user permissions for document type creationReview user/groups permissions in Galette to determine which users have the ability to create or modify document types. Check if any untrusted users have this capability.Affected if Users beyond trusted administrators can modify document types
You are affected if running Galette version 1.2.0 or any version below 1.2.0 AND the Document Type feature is accessible or contains entries.
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 · scoped1.2.0
Upgrade Galette to version 1.2.0 or later. Until upgrade is possible, implement input validation and output encoding on the Document Type field.
Galette 1.2.0 or later
- Verify current Galette version by checking the administration interface or version file
- Backup the database and files before upgrading
- Download Galette version 1.2.0 or later from the official GitHub repository (https://github.com/galette/galette)
- Follow the official upgrade instructions in the documentation to replace the existing installation
- Clear any application caches after upgrade
- Verify the upgrade was successful and test that the Document Type functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48884 — 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-48884 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