dbcve.org
CmsApplication · Schlix

CVE-2025-67443

MEDIUM · 6.1 CVSS v3.1 Published 2025-12-22
Fix available
A fix is available. Upgrade to 2.2.9-5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Schlix CMS before v2.2.9-5 is vulnerable to Cross Site Scripting (XSS). Due to lack of javascript sanitization in the login form, incorrect login attempts in logs are triggered as XSS in the admin panel.

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 confidence

Schlix CMS before v2.2.9-5 contains a stored XSS vulnerability in the login form. When users enter incorrect credentials, the unsanitized input is logged and subsequently rendered in the admin panel's log viewing interface, allowing execution of arbitrary JavaScript in the context of an authenticated administrator's session.

MitigationUpgrade to Schlix CMS v2.2.9-5 or later which implements proper JavaScript sanitization on login form inputs before they are logged and displayed in the admin panel.

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
CmsApplication
Affected:< 2.2.9-5

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Schlix CMS installation
    Check for Schlix CMS files in your web root directory. Look for the typical installation structure including 'index.php', 'app', and 'config' directories. Also check for the presence of a 'schlix-cms' folder or similar installation markers.
    Affected if Schlix CMS is installed on the server.
  2. Identify installed version
    Check the version file or admin dashboard. Look for a version.php file in the installation root or admin area, or log into the admin panel and navigate to the system information or about section to view the CMS version number.
    Affected if The installed version is below 2.2.9-5.
  3. Verify admin panel access
    Access the Schlix CMS admin panel by navigating to /admin or / administrator relative to your installation path. Log in with administrator credentials to confirm you have access to the log viewing interface.
    Affected if You can access the admin panel and view system logs.
  4. Check login failure logging
    Submit incorrect credentials to the login form (the public-facing login page). Then access the admin panel log viewer to see if failed login attempts are recorded and displayed.
    Affected if Failed login attempts are logged and visible in the admin panel log viewer.
  5. Test XSS reflection in logs
    Enter a test script tag such as <script>alert(1)</script> as the username or password in the login form. Submit incorrect credentials. Then view the admin panel logs to see if the script tag is rendered as literal text or executed as JavaScript.
    Affected if The test payload is displayed as rendered HTML/JavaScript in the admin log viewer instead of being escaped.

You are affected if Schlix CMS version is below 2.2.9-5 AND the admin panel log viewer displays unsanitized input from failed login attempts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.2.9-5 or later
Fixed in 2.2.9-5
Interim mitigation

Upgrade to Schlix CMS v2.2.9-5 or later which implements proper JavaScript sanitization on login form inputs before they are logged and displayed in the admin panel.

Recommended fix Moderate confidence

Schlix CMS v2.2.9-5 or later

  1. 1. Backup your current Schlix CMS installation and database before proceeding
  2. 2. Download the latest version of Schlix CMS (v2.2.9-5 or later) from the official source at www.schlix.com
  3. 3. Extract the downloaded package to a temporary location
  4. 4. Replace the existing CMS files with the new version files, preserving your configuration and custom files as needed
  5. 5. Run any available database migration scripts included in the update
  6. 6. Clear any caches if your CMS has caching enabled
  7. 7. Verify the upgrade by attempting to trigger the previously vulnerable login form XSS vector
  8. 8. Check the admin panel logs to confirm the XSS is now properly sanitized

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67443 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67443 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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