dbcve.org
Haxcms PhpApplication · Psu

CVE-2025-32028

CRITICAL · 9.9 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable 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
HAX CMS PHP allows you to manage your microsite universe with PHP backend. Multiple file upload functions within the HAX CMS PHP application call a ’save’ function in ’HAXCMSFile.php’. This save function uses a denylist to block specific file types from being uploaded to the server. This list is non-exhaustive and only blocks ’.php’, ’.sh’, ’.js’, and ’.css’ files. The existing logic causes the system to "fail open" rather than "fail closed." This vulnerability is fixed in 10.0.3.

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

HAXCMS PHP file upload functionality uses an incomplete denylist in HAXCMSFile.php that only blocks .php, .sh, .js, and .css extensions. The system fails open, allowing unrestricted upload of dangerous file types (e.g., .phtml, .php5, .exe, .asp, .jsp, .svg) not on the denylist, leading to remote code execution.

MitigationUpgrade to HAXCMS PHP version 10.0.3 or later. Until upgrade is possible, implement an allowlist-based file upload validation that only permits known-safe file types and rejects everything else.

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
Haxcms PhpApplication
Affected:>= 9.0.0, < 10.0.3

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 HAXCMS PHP version
    Locate the version file, composer.json, or package.json in your HAXCMS installation and read the version number
    Affected if The version is >= 9.0.0 and < 10.0.3
  2. Locate HAXCMSFile.php
    Find the file named HAXCMSFile.php within the HAXCMS codebase, typically in includes or core directories
    Affected if The file exists in your installation
  3. Inspect the denylist implementation
    Open HAXCMSFile.php and search for the file upload validation logic, specifically looking for the list of blocked extensions
    Affected if The denylist only contains .php, .sh, .js, and .css extensions and omits dangerous types like .phtml, .php5, .exe, .asp, .jsp, or .svg
  4. Check if file upload is enabled
    Review the HAXCMS configuration or admin settings to determine if the file upload functionality is enabled for users
    Affected if File uploads are permitted and the denylist in step 3 is in use
  5. Test upload capability with a non-blocked extension
    If you have access, attempt to upload a test file with a .phtml, .asp, .jsp, or .svg extension through the HAXCMS upload interface
    Affected if The upload succeeds and the file is stored on the server

Your environment is affected if HAXCMS PHP version is between 9.0.0 and 10.0.3 and the file upload feature is enabled with the incomplete denylist present.

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

Upgrade to HAXCMS PHP version 10.0.3 or later. Until upgrade is possible, implement an allowlist-based file upload validation that only permits known-safe file types and rejects everything else.

Recommended fix High confidence

10.0.3

  1. Upgrade HAX CMS PHP to version 10.0.3 or later to address the unrestricted file upload vulnerability.
  2. After upgrading, verify that file upload functionality works correctly with allowed file types.
  3. Ensure that the new version uses an allowlist approach rather than a denylist for file type validation.

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

Fix this in Haxcms Php Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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