dbcve.org
AlcasarApplication

CVE-2024-38293

CRITICAL · 9.6 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

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 CSRF and remote code execution in activity.php.

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

ALCASAR before version 3.6.1 contains a cross-site request forgery (CSRF) vulnerability in activity.php that can be chained to achieve remote code execution. An attacker can trick an authenticated administrator into performing unintended actions that result in arbitrary command execution on the affected system.

MitigationUpgrade ALCASAR to version 3.6.1 or later to remediate this vulnerability. Until the upgrade is applied, limit administrative access to trusted networks and monitor for suspicious administrative actions.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed ALCASAR version
    Check the ALCASAR version file or the web interface footer. Common locations: /etc/alcasar/version or look at the admin login page footer. Run: cat /etc/alcasar/conf/version or grep -i version /usr/local/bin/alcasar* 2>/dev/null
    Affected if The installed version is lower than 3.6.1 (e.g., 3.5.x, 3.4.x, etc.)
  2. Verify activity.php is present and accessible
    Check for the presence of activity.php in the web directory. Typical path: /var/www/html/activity.php or /opt/alcasar/www/activity.php. Use: find /var/www -name activity.php 2>/dev/null or ls -la /opt/alcasar/www/activity.php 2>/dev/null
    Affected if activity.php exists on the system and is accessible via the web interface (port 80/443)
  3. Confirm administrator is logged in via web interface
    Check if the ALCASAR admin web interface is accessible and uses session-based authentication. Review the web server logs for active admin sessions: grep -i 'activity.php' /var/log/apache2/access.log 2>/dev/null | head -20
    Affected if Administrative users are logged in or have active sessions on the ALCASAR web interface, making them vulnerable to CSRF attacks
  4. Check if PHP exec/system functions are enabled
    Review PHP configuration for the web server. Check /etc/php/*/apache2/php.ini for disable_functions setting, or examine activity.php source code for system/exec/passthru calls. Run: grep -i 'disable_functions' /etc/php/*/apache2/php.ini 2>/dev/null
    Affected if PHP disable_functions does not block exec, system, passthru, shell_exec, and activity.php contains code that executes system commands based on user input

You are affected if ALCASAR version is below 3.6.1 AND activity.php is present and accessible AND the web interface allows authenticated admin sessions that could be exploited via CSRF to trigger command execution.

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 remediate this vulnerability. Until the upgrade is applied, limit administrative access to trusted networks and monitor for suspicious administrative actions.

Recommended fix High confidence

Alcasar 3.6.1

  1. Backup your current Alcasar configuration and data before starting the upgrade process
  2. Download Alcasar version 3.6.1 from the official sources (adullact.net or alcasar.net)
  3. Follow the official Alcasar upgrade documentation for your current version
  4. Verify the upgrade was successful by checking the version number in the admin interface
  5. Test that the activity.php functionality works correctly post-upgrade
Caveat Review release notes for any configuration changes required during upgrade from pre-3.6.1 versions

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

Fix this in Alcasar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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