dbcve.org
Lemonldap\Application · Lemonldap Ng

CVE-2024-48933

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-09
Fix available
A fix is available. Upgrade to 2.19.3 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
A cross-site scripting (XSS) vulnerability in LemonLDAP::NG before 2.19.3 allows remote attackers to inject arbitrary web script or HTML into the login page via a username if userControl has been set to a non-default value that allows special HTML characters.

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

An XSS vulnerability in LemonLDAP::NG allows remote attackers to inject arbitrary web script or HTML into the login page via the username parameter when userControl is configured to a non-default value that permits special HTML characters. This affects versions before 2.19.3.

MitigationUpgrade to LemonLDAP::NG version 2.19.3 or later. Additionally, review and ensure userControl is not configured to allow special HTML characters.

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
Lemonldap\Application
Affected:< 2.19.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
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. Check LemonLDAP::NG installed version
    Run `dpkg -l | grep lemonldap-ng` or `rpm -qa | grep lemonldap-ng` to list installed packages, or check the version file if available in the installation directory
    Affected if version is lower than 2.19.3
  2. Locate LemonLDAP::NG configuration file
    Find the main configuration file typically at /etc/lemonldap-ng/lemonldap-ng.conf or check the LLNG handler configuration for Config stanza
    Affected if configuration file cannot be located for further userControl检查
  3. Inspect userControl parameter value
    Search for 'userControl' in the LemonLDAP::NG configuration file and note its configured value
    Affected if userControl is set to a value that permits or fails to sanitize special HTML characters such as <, >, or "的程度
  4. Verify username parameter handling on login page
    If possible, review the login handler code or template that processes the username parameter to confirm it reflects user input without proper escaping when userControl permits special characters
    Affected if username input is reflected in the login page response without HTML entity encoding

Affected if LemonLDAP::NG version is below 2.19.3 AND userControl is configured to allow special HTML characters in usernames, enabling XSS injection via the username parameter on the login page.

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.19.3 or later
Fixed in 2.19.3
Interim mitigation

Upgrade to LemonLDAP::NG version 2.19.3 or later. Additionally, review and ensure userControl is not configured to allow special HTML characters.

Recommended fix High confidence

2.19.3

  1. 1. Backup current LemonLDAP::NG configuration and data before proceeding with upgrade
  2. 2. Upgrade LemonLDAP::NG to version 2.19.3 or later using your distribution's package manager or source installation method
  3. 3. After upgrade, verify that userControl configuration does not allow dangerous HTML characters unless intended
  4. 4. Test the login page with various inputs to confirm XSS protection is working
  5. 5. Monitor application logs for any errors following the upgrade

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

Fix this in Lemonldap\ Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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