The Paywall That Wasn't: Debugging a 919-Video Leak on WordPress

Jun 30, 2026 · 7:31 AM UTC ·9 min read · 0 reactions · 0 comments · 26 views

TL;DR · WeSearch summary

A WordPress site experienced a bug where paid members could not access on-demand videos, but it was discovered that the paywall was not protecting the content at all. The issue was caused by a misconfiguration between WishList Member and All-in-One Video Gallery, resulting in 919 videos being publicly accessible. The problem was resolved by implementing a server-side gate before rendering the content.

Key facts

▪The site used a combination of WordPress, WooCommerce, WishList Member, and Vimeo to manage its membership and video content.
▪The bug was initially reported as a simple access-check issue, but it was later discovered that the paywall was not functioning at all.
▪The fix involved implementing a server-side gate to protect the content before it was rendered.
▪The issue was caused by a misconfiguration between WishList Member and All-in-One Video Gallery, which resulted in the content protection not being applied to the videos.
▪The site's use of a custom post type for the videos contributed to the issue, as WishList Member's content protection did not automatically apply to the videos.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/highcenburg/the-paywall-that-wasnt-debugging-a-919-video-leak-on-wordpress-4jae
Publication time	Tue, 30 Jun 2026 07:31:56 +0000
Retrieval time	2026-06-30T07:54:24.163Z
Last seen	2026-06-30T07:54:24.163Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	iZ1Lqi5dEDci
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 126345) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Vicente G. Reyes Posted on Jun 30 • Originally published at vicentereyes.org The Paywall That Wasn't: Debugging a 919-Video Leak on WordPress #wordpress #security #webdev #php The ticket was three sentences long: "Some paid members can't play the on-demand videos. They log in, click a video, and still get told they need a membership. Can you fix it tonight?" I fixed it tonight.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments