Security readout for executives and security teams
Plain-English summary
DocSys-master V2.02.85 reportedly allows unauthenticated attackers to upload arbitrary files through a Markdown image interface. Successful abuse could expose data, alter application content, or disrupt service. The supplied sources do not confirm whether uploaded files can execute, so full system compromise is possible by CVSS assessment but not independently demonstrated here.
Executive priority
Treat confirmed DocSys-master V2.02.85 exposure as an immediate remediation priority, especially when internet-facing. Restrict access while seeking authoritative patch guidance. Investigate for suspicious uploads because the stated impact spans data theft, unauthorized modification, and service disruption, although active exploitation is not currently evidenced.
Technical view
CVE-2026-75327 is a CWE-434 arbitrary file upload issue in uploadMarkdownPic within DocController.java. Its CVSS 3.1 score is 9.8, reflecting network access, low complexity, no privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact. Structured affected-product data and CPE identifiers are unavailable.
Likely exposure
Highest risk applies to internet-accessible DocSys-master V2.02.85 deployments exposing uploadMarkdownPic without compensating authentication or upload controls. Exposure for other versions cannot be established from the supplied evidence. Inventory and endpoint reachability must therefore be verified directly.
Exploitation context
The supplied bundle does not establish active exploitation, and the CVE is not identified as being in KEV. A public technical reference exists, which may increase attacker awareness. No reliable evidence here confirms exploitation in the wild, executable upload placement, or a working public exploit.
Researcher notes
The record identifies a specific controller method and version but lacks normalized vendor, product, CPE, patch, and fixed-version data. CWE-434 supports the upload-control diagnosis. Researchers should distinguish arbitrary storage from executable code placement; the supplied evidence does not establish execution, traversal, overwrite behavior, or affected-version range beyond V2.02.85.
Mitigation direction
- Check project or vendor guidance for an official fix; none is named in the supplied sources.
- Restrict external access to the affected interface until remediation is confirmed.
- Disable the uploadMarkdownPic interface if business operations permit.
- Enforce authentication, strict file allowlisting, safe filenames, and storage outside executable web paths.
- Monitor upload directories and application logs for unexpected files or requests.
Validation and detection
- Identify all DocSys-master deployments and confirm their exact versions.
- Determine whether uploadMarkdownPic is reachable from untrusted networks without authentication.
- Review upload storage for unexpected file types, names, timestamps, or modifications.
- Inspect web, proxy, and application logs for unusual requests to the affected interface.
- After mitigation, verify rejected uploads safely in an isolated test environment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-75327 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.