CVE-2025-14947
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe All-in-One Video Gallery plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `ajax_callback_create_bunny_stream_video`, `ajax_callback_get_bunny_stream_video`, and `ajax_callback_delete_bunny_stream_video` functions in all versions up to, and including, 4.6.4. This makes it possible for unauthenticated attackers to create and delete videos on the Bunny Stream CDN associated with the victim's account, provided they can obtain a valid nonce which is exposed in public player templates.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe All-in-One Video Gallery plugin for WordPress lacks capability checks on three AJAX functions (create, get, and delete bunny stream video) in versions up to 4.6.4. While these AJAX endpoints require a nonce, the nonce is exposed in public player templates, allowing unauthenticated attackers to obtain a valid nonce and use it to create or delete videos on the victim's Bunny Stream CDN account.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installation and versionNavigate to WordPress admin > Plugins and locate 'All-in-One Video Gallery', or check the plugin header file for the version numberAffected if The installed version is 4.6.4 or lower
-
Identify if Bunny Stream integration is activeCheck plugin settings for Bunny Stream CDN configuration (look for Bunny API keys, stream settings, or video source configuration in the plugin admin panel)Affected if Bunny Stream is configured as a video source in the plugin settings
-
Verify AJAX endpoint accessibilityInspect the plugin PHP files for AJAX handlers handling 'create_bunny_stream_video', 'get_bunny_stream_video', and 'delete_bunny_stream_video' actions - check if they include a capability check like 'manage_options' or 'edit_posts'Affected if The AJAX callbacks lack capability checks (e.g., no current_user_can() with appropriate capability) before processing requests
-
Check for nonce exposure in templatesExamine the plugin's public player templates (look in the plugin's templates folder) to see if the AJAX nonce is rendered in publicly accessible HTMLAffected if The nonce value is output in the page source of video player templates visible to unauthenticated users
A user is affected if they have All-in-One Video Gallery plugin version 4.6.4 or lower with Bunny Stream integration enabled and the AJAX endpoints lack proper capability checks with exposed nonces in public templates.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to a patched version that adds proper capability checks (e.g., 'manage_options') to the affected AJAX callbacks and addresses nonce exposure in public templates.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14947 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data