CVE-2025-63694
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 · uneditedDzzOffice v2.3.7 and before is vulnerable to SQL Injection in explorer/groupmanage.
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 confidenceDzzOffice v2.3.7 and earlier contains a SQL Injection vulnerability in the explorer/groupmanage functionality. Attackers can inject malicious SQL queries through unsanitized input parameters in this component, potentially allowing unauthorized database access, data exfiltration, or complete system compromise.
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<= 2.3.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate DzzOffice installationSearch the server for DzzOffice files - common paths include /var/www/html/, /www/wwwroot/, or check web server document roots for a 'dzz' or 'dzzoffice' directory containing core files like core/app.php or index.phpAffected if DzzOffice is not found on the system (not affected)
-
Identify installed DzzOffice versionCheck version.php or version.json in the DzzOffice installation root, or look for a version definition in core/class/coreversion.php or similar version file within the core directoryAffected if Installed version is 2.3.7 or earlier, meaning the vulnerable version range is present
-
Verify explorer/groupmanage is accessibleCheck if the explorer/groupmanage endpoint exists by looking for groupmanage.php or equivalent in the explorer module directory, and confirm the route is active in the application's routing configurationAffected if The explorer/groupmanage component is present and accessible via web requests
-
Confirm vulnerable parameter exposureReview the groupmanage code for unsanitized input parameters - typically look for $_GET, $_POST, or $_REQUEST usage in SQL queries without proper escaping or parameterized queries, especially parameters used in WHERE clausesAffected if Unsanitized user input is directly used in SQL queries within the groupmanage functionality
The environment is affected if DzzOffice version 2.3.7 or earlier is installed AND the explorer/groupmanage component is accessible with unsanitized SQL input parameters present in the code.
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 dataUpgrade to a version beyond v2.3.7 when a patched release is available. Until then, disable the affected explorer/groupmanage endpoint and implement strict input validation with parameterized queries on all database interactions in the codebase.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-63694 — 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-2025-63694 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