CVE-2024-46625
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 · uneditedAn authenticated arbitrary file upload vulnerability in the /documentCache/upload endpoint of InfoDom Performa 365 v4.0.1 allows attackers to execute arbitrary code via uploading a crafted SVG file.
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 confidenceAuthenticated users can upload arbitrary SVG files through the /documentCache/upload endpoint in InfoDom Performa 365 v4.0.1. SVG files can contain embedded malicious scripts or exploit parser vulnerabilities, allowing attackers to execute arbitrary code on the 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 InfoDom Performa 365 installation and versionLocate the installation directory or check system inventory for InfoDom Performa 365. Look for version information in the application metadata, about page, or installation logs.Affected if The installed version is InfoDom Performa 365 v4.0.1 or an unpatched version within this release line.
-
Verify the /documentCache/upload endpoint existsCheck if the web server exposes the /documentCache/upload path. This may be discoverable via web path enumeration, reviewing application routing configuration, or consulting the application's API documentation if available.Affected if The /documentCache/upload endpoint is present and accessible on the server.
-
Confirm file upload functionality is enabledReview application configuration files or settings panel to determine if document/file upload features are enabled for users. Check if any upload-related modules are loaded or active.Affected if File upload functionality is enabled and available to authenticated users.
-
Check if SVG file uploads are permittedInspect the application's allowed file type configuration. Look for file extension validation settings that may explicitly or implicitly allow .svg uploads. Test by attempting to upload an SVG file through the upload endpoint with valid credentials.Affected if SVG files are accepted as valid upload types by the application.
-
Determine if authentication is properly enforced on the endpointAttempt to access the /documentCache/upload endpoint without credentials. Review server logs for authentication enforcement. Check if the endpoint enforces valid session/authentication before processing uploads.Affected if The endpoint accepts uploads from users with valid credentials (as stated in the CVE), meaning authentication is enforced but the vulnerability still exists within that context.
A user is affected if InfoDom Performa 365 v4.0.1 is installed, the /documentCache/upload endpoint is accessible, file uploads are enabled, and SVG files are accepted as valid upload types.
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 dataImplement strict allowlist-based file validation (verify magic bytes, not just extensions), sanitize or reject SVG uploads, store uploaded files outside the webroot, and disable script execution in upload directories.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46625 — 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-46625 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