CVE-2025-1105
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 · uneditedA vulnerability was found in SiberianCMS 4.20.6. It has been rated as problematic. Affected by this issue is some unknown functionality of the file /app/sae/design/desktop/flat of the component HTTP GET Request Handler. The manipulation leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. 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 · moderate confidenceA stored cross-site scripting (XSS) vulnerability exists in SiberianCMS version 4.20.6 within the HTTP GET Request Handler for the /app/sae/design/desktop/flat file. The vulnerability allows remote attackers to inject malicious scripts via unsanitized input, which is then executed in the browsers of other users viewing the affected page. The exploit has been publicly disclosed.
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= 4.20.6CVSS 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.
-
Identify SiberianCMS installation versionLocate the version file or admin panel version indicator in your SiberianCMS installation. Common paths include version.php files in the root directory, or check the admin dashboard 'System Information' or 'About' section.Affected if The installed version is exactly 4.20.6
-
Verify /app/sae/design/desktop/flat endpoint existsAttempt to access the endpoint via HTTP GET request to http(s)://yourdomain.com/app/sae/design/desktop/flat and observe the response.Affected if The endpoint returns a valid HTTP response (200 or similar) indicating the feature is accessible
-
Inspect the page source for unsanitized parametersView the HTML source of the /app/sae/design/desktop/flat page in a browser or via curl. Examine any URL parameters or input fields present in the page for unsanitized user-controlled values.Affected if User-supplied input appears in the page output without proper HTML encoding or sanitization
-
Review application logs for XSS probe attemptsCheck web server access logs and application logs for requests to /app/sae/design/desktop/flat containing suspicious patterns like <script>, javascript:, onerror=, or other XSS payloads.Affected if Logs show recent GET requests to this endpoint containing known XSS attack signatures
You are affected if your SiberianCMS version is exactly 4.20.6 and the /app/sae/design/desktop/flat endpoint is accessible and returns unsanitized user input in its response.
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 robust input validation and output encoding on the affected /app/sae/design/desktop/flat endpoint to neutralize malicious script payloads. Consider deploying a WAF rule to block XSS attack patterns as an interim measure until a vendor patch becomes available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1105 — 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-1105 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