dbcve.org
HomarrApplication

CVE-2025-67493

CRITICAL · 9.0 CVSS v3.1 Published 2025-12-17
Fix available
A fix is available. Upgrade to 1.45.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable

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
Homarr is an open-source dashboard. Prior to version 1.45.3, it was possible to craft an input which allowed privilege escalation and getting access to groups of other users due to missing sanitization of inputs in ldap search query. The vulnerability could impact all instances using ldap authentication where a malicious actor had access to a user account. Version 1.45.3 has a patch for the issue.

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 confidence

This is an LDAP injection vulnerability in Homarr's dashboard where missing input sanitization in the LDAP search query allows authenticated users to escalate privileges and access groups of other users. The attack requires an attacker to have an existing user account on an LDAP-authenticated Homarr instance.

MitigationUpgrade Homarr to version 1.45.3 or later to apply the patch. Review LDAP configuration and monitor for suspicious LDAP queries from existing user accounts.

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
HomarrApplication
Affected:< 1.45.3

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
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

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. Determine installed Homarr version
    Access the Homarr admin interface and navigate to Settings > About, or inspect the container/image metadata if running in Docker/Kubernetes
    Affected if The installed version is prior to 1.45.3
  2. Confirm LDAP authentication is enabled
    Navigate to Settings > Authentication in the Homarr interface and verify an LDAP authentication provider is configured and active
    Affected if LDAP authentication is enabled and the Homarr version is below 1.45.3
  3. Review authentication logs for LDAP query anomalies
    Examine Homarr's authentication and application logs for LDAP search queries containing special characters (e.g., *, (, ), \) that could indicate injection attempts from existing user accounts
    Affected if Suspicious LDAP search patterns are present in logs from authenticated users querying unexpected group memberships

A user is affected if their Homarr instance is version 1.45.2 or earlier AND LDAP authentication is enabled, allowing a known authenticated user to potentially inject malicious LDAP search queries for privilege escalation.

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 1.45.3 or later
Fixed in 1.45.3
Interim mitigation

Upgrade Homarr to version 1.45.3 or later to apply the patch. Review LDAP configuration and monitor for suspicious LDAP queries from existing user accounts.

Recommended fix High confidence

Homarr version 1.45.3

  1. Backup your Homarr data and configuration before upgrading
  2. If using Docker, pull the latest image: docker pull ghcr.io/homarr-labs/homarr:latest or specify version 1.45.3: docker pull ghcr.io/homarr-labs/homarr:1.45.3
  3. Restart the Homarr container to apply the update
  4. If using npm/yarn, run: npm install [email protected] or yarn add [email protected]
  5. After upgrading, verify the new version is running: check the Homarr UI or API
  6. Test LDAP authentication to confirm the fix works correctly
  7. Ensure no unauthorized access to other user groups has occurred
Caveat Review Homarr release notes for version 1.45.3 to check for any breaking changes before upgrading

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

Fix this in Homarr Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,010
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,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67493 — 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-67493 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