CVE-2025-48109
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Xavier Media XM-Backup xm-backup allows Stored XSS.This issue affects XM-Backup: from n/a through <= 0.9.1.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in XM-Backup allows attackers to craft malicious requests that trick authenticated users into performing unintended actions, leading to Stored XSS where malicious scripts are persisted on the server and executed when other users access the affected functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Confirm XM-Backup installationIdentify if XM-Backup or any backup-related module/plugin is installed in your environment. Check for backup configuration files, backup directories, or the presence of XM-Backup in your software inventory.Affected if XM-Backup is present and accessible without further verification of CSRF protections.
-
Inspect form submissions for anti-CSRF tokensExamine the HTML source code or network requests when submitting backup-related forms. Look for hidden token fields or authorization headers in POST/PUT/DELETE requests to backup endpoints.Affected if State-changing backup operations lack anti-CSRF tokens in the request payload.
-
Verify Origin and Referer header validationCheck server configuration or application logs for validation of Origin/Referer headers on backup-related state-changing endpoints. Test by omitting or spoofing these headers in requests.Affected if The application accepts state-changing requests without validating the Origin or Referer header.
-
Test for stored XSS in backup functionalitySubmit a backup job with a malicious script payload in fields such as backup name, description, or destination. Then access the backup list or details as a different user to see if the script executes.Affected if User-supplied input in backup fields is stored and rendered without proper output encoding, allowing script execution.
-
Review input validation on backup parametersAnalyze the application's input handling for backup-related parameters. Check if special characters are filtered or sanitized before storage.Affected if Input fields in the backup functionality accept and persist raw user input without sanitization or validation.
Your environment is affected if XM-Backup is installed and state-changing operations lack anti-CSRF token protection combined with insufficient input validation, allowing stored XSS to be executed.
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.
From vendor dataImplement anti-CSRF tokens and validate Origin/Referer headers on state-changing operations, combined with proper input validation and output encoding to prevent the stored XSS payload execution.
- Consultation2.0 h
- Implementation8.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48109 — 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-48109 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