dbcve.org
ChancmsApplication

CVE-2025-8226

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-27
Fix available
A fix is available. Upgrade to 3.1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 was found in yanyutao0402 ChanCMS up to 3.1.2. It has been classified as problematic. Affected is an unknown function of the file /sysApp/find. The manipulation of the argument accessKey/secretKey leads to information disclosure. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 3.1.3 is able to address this issue. It is recommended to upgrade the affected component.

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 ChanCMS /sysApp/find endpoint improperly exposes accessKey and secretKey arguments, allowing unauthenticated remote attackers to retrieve sensitive authentication credentials via direct request manipulation. The publicly disclosed exploit enables immediate information disclosure with critical CVSS 9.8 impact.

MitigationUpgrade ChanCMS to version 3.1.3 immediately to remediate the information disclosure vulnerability; verify the upgrade removes access to the vulnerable endpoint or properly protects credential parameters.

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
ChancmsApplication
Affected:< 3.1.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
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 installed ChanCMS version
    Locate the version file or admin panel version display in your ChanCMS installation. Check configuration files, package.json, or the admin dashboard for the version number.
    Affected if The installed version is below 3.1.3 (e.g., 3.1.2, 3.1.1, etc.)
  2. Verify vulnerable endpoint exists
    Make a GET or POST request to the /sysApp/find endpoint on your ChanCMS server (e.g., https://yourdomain.com/sysApp/find or http://localhost:port/sysApp/find).
    Affected if The endpoint responds with any HTTP status code other than 404 (not found) or 403 (forbidden), indicating the endpoint is accessible.
  3. Check for credential exposure
    Send a request to /sysApp/find with minimal or empty parameters, and examine the response for any mention of 'accessKey', 'secretKey', or similar credential fields.
    Affected if The response contains plaintext accessKey, secretKey, or other authentication credentials in the JSON or HTML output.
  4. Review server access logs
    Examine web server access logs (Apache/nginx) for requests to /sysApp/find endpoint, looking for patterns that may indicate scanning or exploitation attempts.
    Affected if Recent or historical requests to /sysApp/find are present from unexpected IP addresses, especially without prior authentication.

Your environment is affected if ChanCMS version is below 3.1.3 AND the /sysApp/find endpoint is accessible AND returns credential information.

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

Upgrade ChanCMS to version 3.1.3 immediately to remediate the information disclosure vulnerability; verify the upgrade removes access to the vulnerable endpoint or properly protects credential parameters.

Recommended fix High confidence

ChanCMS 3.1.3

  1. Backup the current Chancms installation and database before proceeding with any changes
  2. Download ChanCMS version 3.1.3 from the official source (gitee.com or the project repository)
  3. Replace the existing Chancms files with the version 3.1.3 files
  4. Verify the /sysApp/find endpoint no longer exposes accessKey/secretKey information
  5. Test that the application functions correctly after the upgrade
  6. Monitor for any unusual behavior or continued information disclosure
Caveat No breaking changes documented in the available vulnerability description

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

Fix this in Chancms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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