Skip to main content
Menu
CVEs

WeddingShare unauthenticated download of gallery media via MediaViewer

CVE-2026-134679Published , updated

8.7HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

WeddingShare through 1.8.2 contains a missing authorization vulnerability in the anonymous MediaViewerController.GalleryItem action that allows unauthenticated attackers to retrieve item upload paths without the gallery secret key. Attackers can enumerate sequential integer item ids to learn paths and uploader names, then download photos and videos from key-protected galleries served as static files.

Who should check

Sites running WeddingShare 1.8.2 or earlier, including the post-1.8.2 commit, in production mode with SQLite and key-protected galleries

“Affected versions: confirmed on commit fa71c361a1824fd1aab32b1d75c441acb8613461 (after release 1.8.2), production mode, SQLite”

github.com

What to do

Workaround: No fix is listed yet. The checked facts do not include a workaround, so limiting access to the site or to affected galleries is the only option the facts support, and the vendor's guidance should be checked.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134679 (WeddingShare through 1.8.2 Missing Authorization via MediaViewer GalleryItem), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134679 (entry last updated 2026-11-22):
Affected:
- Cirx08 WeddingShare: through 1.8.2
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- WeddingShare 1.8.2 or earlier (source: https://www.vulncheck.com/advisories/weddingshare-through-1.8.2-missing-authorization-via-mediaviewer-galleryitem)
- Confirmed in production mode with SQLite; MySQL and reverse-proxy setups were not tested (source: https://github.com/Cirx08/WeddingShare/issues/199)
- Target photos sit in galleries protected by a secret key (source: https://www.vulncheck.com/advisories/weddingshare-through-1.8.2-missing-authorization-via-mediaviewer-galleryitem)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134679 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134679 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Cirx08/WeddingShare/issues/199
- https://github.com/Cirx08/WeddingShare/blob/1.8.2/WeddingShare/Controllers/MediaViewerController.cs#L18-L100
- https://www.vulncheck.com/advisories/weddingshare-through-1.8.2-missing-authorization-via-mediaviewer-galleryitem
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134679
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134679"}.

Affected versions

cve.now Index

31Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active
  • Would score about 36 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

Questions about CVE-2026-134679

Is CVE-2026-134679 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

Unauthenticated users can download approved photos and videos from key-protected galleries by enumerating item ids, without the gallery key. They can also learn uploaders' display names, but no write or admin access is gained.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134679?

WeddingShare: through 1.8.2.

Source: cve.now feed data

Am I affected, and how do I check?

WeddingShare 1.8.2 and earlier are affected, as confirmed in production mode with SQLite. MySQL and reverse-proxy setups were not tested. To check, look at the installed WeddingShare version and whether the site runs in production mode with SQLite.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134679?

No fixed version is listed in the checked facts, so no upgrade target is given. Watch the vendor's advisory for a patch.

Source: vulncheck.com, github.com

What if there's no patch?

No fix is listed yet. The checked facts do not include a workaround, so limiting access to the site or to affected galleries is the only option the facts support, and the vendor's guidance should be checked.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.