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

> Attackers can predict delete codes using weak randomness to unauthorizedly delete hosted files in PictShare.

- **Severity:** High 8.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-6654-r2c2-m62r

## What is CVE-2026-104356?

CVE-2026-104356 is a high-severity vulnerability in HaschekSolutions pictshare, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2026-104356?


## How do I fix CVE-2026-104356?

No fix has been published for CVE-2026-104356 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-104356 being exploited?

There is no known exploitation of CVE-2026-104356 in the wild and no public exploit code.

Public exploit code:

- Predictable delete_code via rand() in PictShare < 3.7.1 (CWE-338). PoC + advisory writeup. (github_poc): https://github.com/wvllxe/CVE-2026-104356-pictshare-weak-delete-code

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104356 and fix it if it is affected.

What it is: CVE-2026-104356 is a high-severity vulnerability in HaschekSolutions pictshare, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-104356 in the wild and no public exploit code.

Affected product: HaschekSolutions pictshare. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104356/ (Markdown: https://insights.sbomify.com/CVE-2026-104356/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104356
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104356
- OSV: https://osv.dev/vulnerability/CVE-2026-104356

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104356/
Summaries are generated and may contain mistakes; the official description above is the record.