dbcve.org
JeecgApplication

CVE-2021-37306

HIGH · 7.5 CVSS v3.1 Published 2023-02-03
Fix available
A fix is available. Upgrade to after 2.4.5 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
An Insecure Permissions issue in jeecg-boot 2.4.5 and earlier allows remote attackers to gain escalated privilege and view sensitive information via api uri: api uri:/sys/user/checkOnlyUser?username=admin.

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

The jeecg-boot application version 2.4.5 and earlier has an insecure permissions vulnerability in the /sys/user/checkOnlyUser API endpoint. This endpoint allows unauthenticated remote attackers to check if user accounts exist (e.g., username=admin), enabling reconnaissance for further attacks and potential privilege escalation.

MitigationApply authentication and authorization controls to the /sys/user/checkOnlyUser endpoint and audit similar endpoints for the same vulnerability. Upgrade to version 2.4.6 or later if a patched version is available.

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
JeecgApplication
Affected:<= 2.4.5

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 jeecg-boot installation
    Search for jeecg-boot JAR files, application directories, or running processes. Check web server document roots for jeecg-boot WAR deployments.
    Affected if jeecg-boot application is present in the environment
  2. Determine installed version
    Check the application version in pom.xml, version.properties, or the WAR file manifest. Also check the about/version page if the application has a web UI.
    Affected if version is 2.4.5 or earlier
  3. Verify endpoint exposure
    Send a GET request to http://[host]/sys/user/checkOnlyUser without any authentication headers or session cookies.
    Affected if the endpoint responds without requiring authentication (HTTP 200 or error response rather than 401/403)
  4. Test for user enumeration
    Send a request with a parameter like username=admin to the /sys/user/checkOnlyUser endpoint and observe the response. For example: GET /sys/user/checkOnlyUser?username=admin
    Affected if the response indicates whether the specified username exists (e.g., returns user details, a boolean flag, or different status codes for existing vs non-existing users)

If jeecg-boot version 2.4.5 or earlier is running AND the /sys/user/checkOnlyUser endpoint is accessible without authentication and allows username enumeration, the environment is affected by this CVE.

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 2.4.5
Interim mitigation

Apply authentication and authorization controls to the /sys/user/checkOnlyUser endpoint and audit similar endpoints for the same vulnerability. Upgrade to version 2.4.6 or later if a patched version is available.

Recommended fix Moderate confidence

jeecg-boot 3.0 or latest stable release

  1. 1. Back up your current jeecg-boot installation and database
  2. 2. Check the official Jeecg-boot GitHub repository (github.com/jeecgboot/jeecg-boot) for the latest stable release
  3. 3. Upgrade to jeecg-boot version 3.0 or later, which includes security fixes for authorization vulnerabilities
  4. 4. After upgrade, verify that the /sys/user/checkOnlyUser endpoint requires authentication
  5. 5. Test that unauthorized users cannot access sensitive user information via API endpoints
  6. 6. Review all API endpoints for proper authentication and authorization controls
Caveat Major version upgrade may include breaking changes to APIs, database schema, and configuration; review migration guide before upgrading

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

Fix this in Jeecg Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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