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

Back
New CVE Detected

CVE-2026-104051 – Information Disclosure (Delete Code Leak) – PictShare 2.0.0 through 3.7.0

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-104051 is an information disclosure vulnerability (CWE-522: Insufficiently Protected Credentials) in PictShare, a self-hosted image/file-sharing application. The API::info() endpoint returns the complete raw metadata object for an uploaded file — including the secret delete_code and uploader details — to any unauthenticated caller who knows the file’s hash, allowing that caller to subsequently delete the file. The issue is rated HIGH severity (CVSS v4.0 base score 8.8).

Technical details

  • Root cause: API::info() returned the full contents of the file’s meta.json metadata object without a field whitelist, instead of only non-sensitive fields.
  • The returned object included delete_code (the secret token required to delete a file), along with the uploader’s IP address, User-Agent, remote port, and the file’s SHA-1 hash.
  • Trigger condition: an attacker only needs the publicly visible file hash (e.g., obtained from a shared PictShare link) and calls the info API endpoint for that hash — no authentication or special privileges are required.
  • Attack vector: network, via unauthenticated HTTP requests to the PictShare API.
  • Impact: the disclosed delete_code can be replayed against the delete API to permanently delete arbitrary files, resulting in loss of content integrity/availability; the exposed uploader IP, User-Agent, remote port, and hash also constitute a privacy/information disclosure impact.
  • Related hardening in the same fix: the delete-code comparison previously used a loose == check and treated an unset MASTER_DELETE_CODE (empty string by Docker default) as a valid match, which could allow deletion of files with no delete code set; and delete codes were generated with rand() rather than a cryptographically secure generator.

Affected software

  • PictShare (HaschekSolutions) versions 2.0.0 up to, but not including, 3.7.1

Severity

  • CVSS v3.1 Base Score: 8.2 (HIGH) — Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
  • CVSS v4.0 Base Score: 8.8 (HIGH) — Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade PictShare to version 3.7.1 or later, which whitelists the fields returned by the info API, enforces strict delete-code comparison via hash_equals(), rejects empty delete codes, and switches delete-code generation to random_int().
  • Note: Delete codes issued before upgrading are not automatically rotated by the patch; administrators should treat previously issued delete codes as potentially exposed.
  • If immediate patching is not possible: restrict network access to the PictShare instance (e.g., via firewall rules, VPN, or authentication proxy) to reduce exposure to unauthenticated attackers, and monitor logs for unexpected delete operations.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge