dbcve.org
AlcasarApplication

CVE-2024-38294

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 3.6.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
ALCASAR before 3.6.1 allows email_registration_back.php remote code execution.

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

A remote code execution vulnerability exists in the email_registration_back.php file of ALCASAR, an open-source captive portal authentication system. This flaw allows unauthenticated attackers to execute arbitrary code on the affected system by exploiting the email registration functionality. The vulnerability affects all versions prior to 3.6.1.

MitigationUpgrade ALCASAR to version 3.6.1 or later to address the vulnerability. If immediate patching is not possible, restrict network access to the ALCASAR management interfaces and implement web application firewall rules to block requests to the vulnerable PHP endpoint.

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
AlcasarApplication
Affected:< 3.6.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify ALCASAR version
    Locate the ALCASAR version file or check the system information (common locations include /usr/local/etc/alcasar.conf, /etc/alcasar version file, or the web interface status page). Compare the installed version number to 3.6.1.
    Affected if The installed version is less than 3.6.1 (e.g., 3.5.x, 3.4.x, or any earlier release).
  2. Locate vulnerable PHP file
    Check if the file email_registration_back.php exists in the web root directory. Common paths may include /var/www/html/, /opt/alcasar/www/, or the ALCASAR web interface directory. Search for the file using: find / -name 'email_registration_back.php' 2>/dev/null
    Affected if The file email_registration_back.php exists on the system.
  3. Verify email registration feature is active
    Check the ALCASAR configuration to determine if the email registration/-self-service portal feature is enabled. Look for related settings in alcasar.conf or the admin interface under User Management or Portal settings.
    Affected if The email registration or self-service portal feature is enabled and accessible to unauthenticated users.
  4. Review web server access logs
    Examine web server access logs (typically Apache or Nginx logs in /var/log/) for any suspicious requests to email_registration_back.php, especially those containing code execution patterns (system, exec, passthru, shell_exec, base64 decode patterns).

A system is affected if it runs ALCASAR version lower than 3.6.1 AND has the email_registration_back.php file present with the email registration feature accessible.

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

Upgrade ALCASAR to version 3.6.1 or later to address the vulnerability. If immediate patching is not possible, restrict network access to the ALCASAR management interfaces and implement web application firewall rules to block requests to the vulnerable PHP endpoint.

Recommended fix High confidence

ALCASAR 3.6.1

  1. Download ALCASAR version 3.6.1 or later from the official sources (alcasar.net or adullact.net)
  2. Review the official ALCASAR upgrade documentation for your current version
  3. Perform the upgrade following the documented upgrade procedure
  4. Verify the upgrade was successful by checking the ALCASAR version
  5. Confirm the email_registration_back.php file has been updated to the patched version

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

Fix this in Alcasar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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