dbcve.org
AbcdApplication · Abcd Community

CVE-2024-8410

HIGH · 7.5 CVSS v3.1 Published 2024-09-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
A vulnerability classified as problematic was found in ABCD ABCD2 up to 2.2.0-beta-1. This vulnerability affects unknown code of the file /abcd/opac/php/otros_sitios.php. The manipulation of the argument sitio leads to path traversal. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 path traversal vulnerability exists in ABCD ABCD2 up to 2.2.0-beta-1 in the /abcd/opac/php/otros_sitios.php file. The 'sitio' parameter is not properly validated, allowing an attacker to manipulate path references using '../' sequences to access files outside the intended directory. This can lead to unauthorized file disclosure.

MitigationImplement strict input validation on the 'sitio' parameter, including whitelist-based validation, removal of path traversal sequences ('../'), and enforcement of allowed path prefixes to ensure only intended files can be accessed.

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
AbcdApplication
Affected:= 2.2.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Identify ABCD2 installation and version
    Locate the ABCD installation directory and check for version information files (such as version.php, config files, or about pages). Common paths include /abcd/, /var/www/html/abcd/, or within the web root. Look for version indicators like '2.2.0', '2.2.0-beta-1', or similar version markers.
    Affected if The installed version is 2.2.0-beta-1 or any earlier version up to and including 2.2.0 (note: version 2.2.0 is explicitly listed as affected).
  2. Verify vulnerable file exists
    Check if the file /abcd/opac/php/otros_sitios.php exists in the web accessible directory. This is the specific file containing the path traversal vulnerability.
    Affected if The file /abcd/opac/php/otros_sitios.php exists on the server and is web-accessible.
  3. Inspect parameter handling in otros_sitios.php
    Examine the source code of otros_sitios.php to see how the 'sitio' parameter is processed. Look for whether the parameter is used in file operations (include, require, file_get_contents, fopen, etc.) without sanitization.
    Affected if The 'sitio' parameter is used in file inclusion or reading operations without proper validation or path traversal filtering.
  4. Check for missing path traversal protection
    Search the otros_sitios.php code for any filtering of '../' sequences, absolute path restrictions, or whitelist validation applied to the 'sitio' parameter before use.
    Affected if No filtering of '../' sequences, no path prefix enforcement, and no whitelist validation is found in the code handling the 'sitio' parameter.

You are affected if ABCD ABCD2 version 2.2.0 or earlier is installed, the file /abcd/opac/php/otros_sitios.php exists, and the 'sitio' parameter lacks proper input validation to block path traversal sequences.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the 'sitio' parameter, including whitelist-based validation, removal of path traversal sequences ('../'), and enforcement of allowed path prefixes to ensure only intended files can be accessed.

Fix this in Abcd Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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