CVE-2024-10290
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 · uneditedA vulnerability, which was classified as problematic, was found in ZZCMS 2023. This affects an unknown part of the file 3/qq-connect2.0/API/com/inc.php. The manipulation leads to information disclosure. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
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 confidenceA high-severity information disclosure vulnerability was identified in ZZCMS 2023 within the QQ Connect integration file (3/qq-connect2.0/API/com/inc.php). The vulnerability is remotely exploitable and allows unauthorized access to sensitive information through the affected component.
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= 2023CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Zzcms installation versionLocate the Zzcms installation directory and check for version files or identifiers. Common locations include a version.php file, footer/header includes, or the admin dashboard about page. Look for '2023' or the specific Zzcms 2023 release identifier.Affected if The installed Zzcms version is 2023 (any sub-release within the 2023 version line).
-
Verify QQ Connect integration file existsCheck for the presence of the file at path '3/qq-connect2.0/API/com/inc.php' within the Zzcms web root directory. List the directory contents to confirm the qq-connect2.0 folder structure exists.Affected if The file 3/qq-connect2.0/API/com/inc.php exists in the Zzcms installation directory.
-
Inspect the inc.php file for sensitive data exposureOpen and review the contents of 3/qq-connect2.0/API/com/inc.php. Look for hardcoded credentials, API keys, tokens, database connection strings, or any configuration values that should not be publicly accessible.Affected if The inc.php file contains exposed sensitive information such as API keys, credentials, tokens, or configuration data that should be protected.
-
Check file permissions and web accessibilityVerify the file permissions on 3/qq-connect2.0/API/com/inc.php and confirm whether it is accessible via HTTP/HTTPS requests without authentication. Attempt to access the file directly through a web browser or curl command.Affected if The inc.php file is directly accessible via web requests without requiring authentication.
A user is affected if they are running Zzcms 2023 AND have the QQ Connect integration folder present with the inc.php file accessible, which exposes sensitive information.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataRestrict access to the QQ Connect integration file and implement proper authentication/authorization checks. Review the inc.php file for exposed sensitive data and apply appropriate input validation or access controls.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10290 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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