CVE-2025-66837
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 file upload vulnerability in ARIS 10.0.23.0.3587512 allows attackers to execute arbitrary code via uploading a crafted PDF file/Malware
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 ARIS 10.0.23.0.3587512 allows unauthenticated or authenticated attackers to execute arbitrary code by uploading crafted PDF files containing malicious payloads. The application fails to properly validate the content type and contents of uploaded PDF files before storing them in an accessible location, allowing uploaded files to be executed rather than just downloaded.
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<= 10.0.23.0.3587512CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/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 installed ARIS versionLocate the ARIS installation directory and check the version file or application metadata. Common locations include the installation root or help/about section within the application. Compare the version number to 10.0.23.0.3587512.Affected if The installed version is 10.0.23.0.3587512 or any version equal to or lower than this release.
-
Verify file upload functionality existsLocate the file upload module or endpoint within the ARIS web application. This is typically found in document management, import/export, or report generation features. Check if the upload functionality is accessible to users.Affected if File upload functionality is present and accessible to unauthenticated or authenticated users.
-
Confirm PDF upload is acceptedTest or inspect the upload mechanism to determine if PDF files are accepted as an allowed file type. Review the application's file type whitelist or upload configuration settings.Affected if PDF files can be uploaded through the application without proper content validation.
-
Check uploaded file storage locationExamine the web server configuration and file system to determine where uploaded PDF files are stored. Verify if they are placed in a web-accessible directory that allows execution.Affected if Uploaded PDF files are stored within the web root or in a directory accessible via HTTP/HTTPS that permits script execution.
-
Inspect content type validationReview the application's upload handling code or configuration to determine if it validates the actual content (magic bytes) of uploaded files versus only checking the Content-Type header.Affected if The application relies solely on the Content-Type header without verifying the actual file content or uses insufficient validation that can be bypassed.
You are affected if running ARIS version 10.0.23.0.3587512 or lower AND the file upload feature allows PDF files to be uploaded and stored in a web-accessible location with execution capability.
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 file validation including magic byte verification, store uploads outside the web root with randomized filenames, and disable PDF execution capabilities in the upload directory. Consider implementing a file upload sandbox or malware scanning before files are made accessible.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66837 — 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-66837 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