Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-76157 – Unauthenticated Arbitrary File Upload – Datiphy Data Management Center v8.3.0–v8.5.

Be the first to know when new zero-days emerge:

Summary

CVE-2026-76157 is a missing authentication vulnerability (CWE-306) affecting the upload API endpoint of Datiphy Data Management Center. The flaw allows an unauthenticated, remote attacker to upload arbitrary files to the server’s configured upload directory without any credentials or user interaction. The issue carries a High severity rating (8.8) and affects versions 8.3.0 through 8.5.1.

Technical details

  • Root cause: The upload API endpoint in Datiphy Data Management Center does not enforce authentication before accepting file upload requests.
  • Trigger conditions: An attacker sends a crafted request to the exposed upload API endpoint; no valid session, credentials, or prior authentication is required.
  • Attack vector: Network — the endpoint can be reached remotely over the network with no privileges and no user interaction required.
  • Impact: Arbitrary files can be written to the server’s configured upload directory, which can be leveraged to compromise data integrity and system availability (e.g., planting malicious content, overwriting files, or disrupting service).

Affected software

  • Datiphy Data Management Center — versions v8.3.0 through v8.5.1

Severity

  • CVSS Score: 8.8 (High)
  • CVSS v4.0 Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: At the time of publication, no vendor-issued patched version has been confirmed in the public CVE record. Organizations running Datiphy Data Management Center v8.3.0–v8.5.1 should contact Datiphy Inc. directly to confirm availability of a fixed release and apply it as soon as it is issued.
  • If no patch is available:
    • Restrict network access to the Datiphy Data Management Center upload API endpoint to trusted, internal hosts only (e.g., via firewall rules or network segmentation), removing any direct internet exposure.
    • Place the upload endpoint behind an authenticating reverse proxy or gateway that enforces credential checks before requests reach the application.
    • Monitor the configured upload directory for unexpected or unauthorized files, and enable logging/alerting on upload API activity.
    • Consider disabling the upload functionality entirely if it is not business-critical until a fix is confirmed.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge