CVE-2024-48694
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 · uneditedFile Upload vulnerability in Xi'an Daxi Information technology OfficeWeb365 v.8.6.1.0 and v7.18.23.0 allows a remote attacker to execute arbitrary code via the pw/savedraw 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 · moderate confidenceA file upload vulnerability in the pw/savedraw component of OfficeWeb365 versions 8.6.1.0 and v7.18.23.0 allows remote attackers to upload malicious files and achieve arbitrary code execution on the affected server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify OfficeWeb365 installation and versionCheck the application or web server for OfficeWeb365 files. Look for version information in application headers, about pages, or configuration files. Compare your installed version against 8.6.1.0 and v7.18.23.0.Affected if The installed version matches 8.6.1.0 or v7.18.23.0 exactly, or falls within the range between these versions.
-
Locate the pw/savedraw endpointTest if the endpoint /pw/savedraw is accessible on your server by sending a GET or POST request to it. Check your web server logs and routing configuration for this path.Affected if The /pw/savedraw endpoint responds to requests and exists in your deployment.
-
Verify if file upload functionality is enabledInspect the server configuration to determine if the file upload feature tied to the pw/savedraw component is active. Check application settings or module configurations that control upload capabilities.Affected if The file upload function in the pw/savedraw component is currently enabled and operational.
-
Check access controls on the pw/savedraw endpointReview authentication requirements, IP restrictions, or other access controls applied to the /pw/savedraw path in your web server, WAF, or application firewall settings.Affected if The endpoint is publicly accessible without authentication or proper authorization controls.
You are affected if your OfficeWeb365 version is 8.6.1.0 or v7.18.23.0 (or between these versions) AND the /pw/savedraw endpoint is exposed and the file upload feature is enabled without adequate access restrictions.
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 dataApply vendor-provided patches if available; otherwise, disable or restrict access to the pw/savedraw endpoint and implement strict file type validation and upload restrictions as compensating controls.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48694 — 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-48694 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