CVE-2025-48076
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. Versions 1.1.5.2 and below allow a user to edit a group name and insert an XSS payload. 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 · high confidenceGalette versions 1.1.5.2 and below contain a stored Cross-Site Scripting (XSS) vulnerability in the group name edit functionality. An authenticated user can inject malicious JavaScript code into a group name, which executes when other users view the affected group.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Determine Galette versionCheck the version.php file in the Galette installation root directory, or look for a version indicator in the admin dashboard under 'About' or 'Configuration' sectionAffected if Installed version is earlier than 1.2.0 (e.g., 1.1.5.2, 1.1.5.1, etc.)
-
Verify authentication accessConfirm you have an authenticated user account with access to group management features (typically admin or manager roles)Affected if User has authenticated access to group creation or editing functionality
-
Inspect group names in databaseQuery the database (typically MySQL/PostgreSQL) for groups table; look for group_name fields containing HTML tags, script tags, or JavaScript event handlers (onclick, onerror, etc.)Affected if Any group names contain raw HTML/JavaScript code such as <script>, onerror=, or similar XSS payloads that would execute when viewed
-
Check group listing in UINavigate to the groups list page as an authenticated user and view existing groups; inspect page source for unescaped group namesAffected if Group names render as raw HTML or contain executable JavaScript when viewed in the browser
A user is affected if they run a Galette version below 1.2.0 AND have groups in the system whose names contain unescaped HTML or JavaScript code that could execute in other users' browsers.
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 to Galette version 1.2.0 or later, which implements proper input sanitization for group names to prevent XSS injection.
Galette 1.2.0 or later stable release
- 1. Back up your Galette database and files before upgrading.
- 2. Download Galette version 1.2.0 (or a later stable release if available) from the official GitHub repository.
- 3. Replace the existing Galette installation files with the new version.
- 4. Run any database migration scripts included in the upgrade.
- 5. Verify that the XSS fix is applied by attempting to create/edit a group name with a test script payload (e.g., <script>alert(1)</script>) and confirm it is properly escaped or sanitized.
- 6. Clear any application caches if configured.
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-48076 — 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-48076 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