High · CVSS 8.2CVE-2026-104356

PictShare < 3.7.1 Predictable Delete Code via rand()

Answer in brief

CVE-2026-104356 records a High severity (CVSS 8.2) vulnerability in PictShare < 3.7.1 Predictable Delete Code via rand(). The current sources do not mark it as known exploited. The current feed maps HaschekSolutions/pictshare (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 1, 2026Updated Oct 1, 2026Source checked Oct 2, 2026First seen by HOL Oct 1, 2026Material review Oct 1, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.2
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps HaschekSolutions/pictshare (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
HaschekSolutions/pictsharegeneric	>=2.0.0 <3.7.1	3.7.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for HaschekSolutions/pictshare.
Review the reported fix. Update HaschekSolutions/pictshare to 3.7.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 1, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 1, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 1, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.