dbcve.org
HustojApplication

CVE-2026-24479

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-27
Fix available
A fix is available. Upgrade to 26.01.24 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
HUSTOF is an open source online judge based on PHP/C++/MySQL/Linux for ACM/ICPC and NOIP training. Prior to version 26.01.24, the problem_import_qduoj.php and problem_import_hoj.php modules fail to properly sanitize filenames within uploaded ZIP archives. Attackers can craft a malicious ZIP file containing files with path traversal sequences (e.g., ../../shell.php). When extracted by the server, this allows writing files to arbitrary locations in the web root, leading to Remote Code Execution (RCE). Version 26.01.24 contains a fix for 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

Path traversal vulnerability in HUSTOF's problem_import_qduoj.php and problem_import_hoj.php modules allows attackers to craft malicious ZIP archives containing filenames with '../' sequences (e.g., ../../shell.php). When extracted, files are written to arbitrary locations in the web root, achieving remote code execution.

MitigationUpgrade to version 26.01.24 or later which contains the fix for proper filename sanitization in ZIP archive extraction.

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
HustojApplication
Affected:< 26.01.24

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 Hustoj version
    Locate the version file in the Hustoj installation directory or check the admin dashboard for the current version number
    Affected if The installed version is earlier than 26.01.24
  2. Locate vulnerable import modules
    Search for problem_import_qduoj.php and problem_import_hoj.php files in the web root directory, typically under the /admin or /include paths
    Affected if These PHP files exist in the installation
  3. Check web accessibility of vulnerable files
    Attempt to access the problem_import_qduoj.php and problem_import_hoj.php endpoints via HTTP request (e.g., /admin/problem_import_qduoj.php)
    Affected if The files are accessible via web browser without authentication or with valid admin credentials
  4. Verify problem import feature is enabled
    Check if the problem import functionality is active in the admin panel or if the modules can be invoked
    Affected if The import feature can be invoked or is not explicitly disabled in configuration

A user is affected if running Hustoj version earlier than 26.01.24 AND the problem_import_qduoj.php or problem_import_hoj.php modules are web-accessible and functional.

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 26.01.24 or later
Fixed in 26.01.24
Vendor patch github.com →
Interim mitigation

Upgrade to version 26.01.24 or later which contains the fix for proper filename sanitization in ZIP archive extraction.

Recommended fix High confidence

26.01.24

  1. 1. Back up the entire Hustoj installation directory and database before proceeding with the upgrade
  2. 2. Download the fixed version 26.01.24 from the official repository at https://github.com/zhblue/hustoj
  3. 3. Replace the existing problem_import_qduoj.php and problem_import_hoj.php files with the fixed versions from commit 902bd09e6d0011fe89cd84d4236899314b33101f, or upgrade the entire installation to version 26.01.24
  4. 4. Verify that the new files contain the path traversal protection by checking that filenames are properly sanitized before extraction
  5. 5. Test the problem import functionality with a legitimate ZIP file to ensure normal operation is restored
  6. 6. Clear any server caches and restart PHP-FPM/apache if applicable

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

Fix this in Hustoj Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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