dbcve.org
Huaxia ErpApplication · Huaxiaerp

CVE-2024-0491

HIGH · 7.5 CVSS v3.1 Published 2024-01-13
Fix available
A fix is available. Upgrade to after 3.1 or later.
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 has been found in Huaxia ERP up to 3.1. Affected is an unknown function of the file src/main/java/com/jsh/erp/controller/UserController.java. The manipulation leads to weak password recovery. It is possible to launch the attack remotely. Upgrading to version 3.2 is able to address this issue. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-250596.

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

A weak password recovery mechanism in Huaxia ERP's UserController.java (versions up to 3.1) allows remote attackers to potentially reset or discover user passwords through a flawed recovery workflow. The vulnerability is exploitable over the network without authentication.

MitigationUpgrade Huaxia ERP from version 3.1 or earlier to version 3.2 or later, which contains the security fix for the weak password recovery vulnerability.

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
Huaxia ErpApplication
Affected:<= 3.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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 if Huaxia ERP is deployed
    Check for presence of Huaxia ERP application files, or look for web application responses containing 'Huaxia' or 'ERP' in headers/title, or check running services on common application ports (8080, 8443, 80, 443)
    Affected if The system is running Huaxia ERP web application
  2. Determine the installed Huaxia ERP version
    Check application configuration files, about page, or API endpoint that reveals version information; common paths include version files in the WEB-INF or config directories, or the application's login/about page
    Affected if The installed version is 3.1 or earlier (e.g., 3.0, 2.x, 1.x)
  3. Verify the password recovery endpoint is accessible
    Attempt to access the password recovery URL (typically /user/forgotPassword, /user/resetPassword, or similar paths under the UserController), or check web application firewall logs for requests to password recovery endpoints
    Affected if The password recovery endpoint is exposed and reachable over the network without authentication
  4. Check UserController.java configuration
    If code access is available, review UserController.java for the password recovery implementation; look for weak token generation, predictable values, or lack of proper validation in the reset flow
    Affected if The password recovery mechanism uses weak or predictable tokens, lacks rate limiting, or has insufficient validation
  5. Test password recovery workflow
    If authorized, initiate a password recovery request and observe whether the reset token is predictable, emailed in plain text, or uses weak validation (e.g., no expiration, no secret questions)
    Affected if The recovery mechanism allows password reset without proper identity verification or uses weak security controls

The environment is affected if Huaxia ERP version 3.1 or earlier is running and the password recovery functionality is accessible over the network without authentication.

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 a release after 3.1
Interim mitigation

Upgrade Huaxia ERP from version 3.1 or earlier to version 3.2 or later, which contains the security fix for the weak password recovery vulnerability.

Recommended fix High confidence

3.2

  1. Backup the current Huaxia ERP database and application files before upgrading
  2. Download Huaxia ERP version 3.2 or later from the official vendor source
  3. Stop the Huaxia ERP application service
  4. Replace the existing application files with the new version 3.2 files
  5. Run any database migration scripts if provided with the upgrade package
  6. Restart the Huaxia ERP application service
  7. Verify the upgrade was successful by logging into the application
  8. Test the password recovery functionality to confirm the vulnerability is fixed
Caveat Review release notes for version 3.2 to check for any breaking changes or required configuration updates

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

Fix this in Huaxia Erp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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