dbcve.org
VclApplication · Apache

CVE-2024-53679

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-25
Fix available
A fix is available. Upgrade to 2.5.2 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache VCL in the User Lookup form. A user with sufficient rights to be able to view this part of the site can craft a URL or be tricked in to clicking a URL that will give a specified user elevated rights. This issue affects all versions of Apache VCL through 2.5.1. Users are recommended to upgrade to version 2.5.2, which fixes 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

Stored Cross-site Scripting (XSS) vulnerability in the User Lookup form of Apache VCL allows an authenticated user with sufficient rights to inject malicious scripts. When other users access the affected page, the injected script executes, potentially allowing the attacker to escalate privileges by granting specified users elevated rights.

MitigationUpgrade to Apache VCL version 2.5.2, which contains the fix for this XSS vulnerability.

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
VclApplication
Affected:>= 2.1, < 2.5.2

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Determine installed Apache VCL version
    Locate the VCL version file or check the version reported in the VCL admin interface, typically found in the software documentation or via a version command if available
    Affected if The installed version is 2.1 or higher but lower than 2.5.2
  2. Verify User Lookup form is accessible
    Log into the VCL management interface and navigate to the User Lookup functionality, typically found under user management or administration sections
    Affected if The User Lookup form is present and accessible in the current installation
  3. Confirm user has administrative privileges
    Check the permissions of the currently logged-in user account within the VCL system, looking for rights that allow user management or privilege modification
    Affected if The authenticated user has sufficient rights to access user management features and potentially grant elevated rights to other users
  4. Review user account creation and modification logs
    Examine VCL audit logs or user management logs for any unauthorized privilege escalations or unexpected user right modifications
    Affected if There are records of unexpected privilege grants or user right modifications that were not initiated by an authorized administrator

A user is affected if Apache VCL version is 2.1 or higher but below 2.5.2, the User Lookup form is accessible, and an authenticated user with elevated privileges exists in the system who could exploit the stored XSS vulnerability.

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.5.2 or later
Fixed in 2.5.2
Interim mitigation

Upgrade to Apache VCL version 2.5.2, which contains the fix for this XSS vulnerability.

Recommended fix High confidence

2.5.2

  1. Upgrade Apache VCL to version 2.5.2 by following the official upgrade documentation for your deployment method

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

Fix this in Vcl Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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