Photo Gallery BuilderWordPress extension · Wpdiscover
CVE-2024-49325
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 · uneditedMissing Authorization vulnerability in wpdiscover Photo Gallery Builder photo-gallery-builder allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Photo Gallery Builder: from n/a through <= 3.0.
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 · moderate confidenceThe Photo Gallery Builder WordPress plugin (versions <= 3.0) has a missing authorization vulnerability allowing users to access functionality not properly constrained by access control lists. This is a Broken Access Control (BAC) issue where the plugin fails to verify user permissions before executing certain sensitive operations, potentially allowing unauthenticated or lower-privileged users to perform actions reserved for administrators.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Photo Gallery BuilderWordPress extension
<= 3.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 dashboard > Plugins > Installed Plugins. Locate 'Wpdiscover Photo Gallery Builder' and note the version number displayed. Alternatively, inspect the plugin's main PHP file in wp-content/plugins/ and check the 'Version' header comment.Affected if The installed version is 3.0 or lower (any version up to and including 3.0).
-
Verify WordPress user roles existGo to WordPress admin dashboard > Users > All Users. Review the list of existing user accounts and their assigned roles (e.g., Administrator, Editor, Author, Contributor, Subscriber).Affected if There are multiple user accounts with roles other than Administrator, especially Editor, Author, or Contributor roles.
-
Check for sensitive plugin functionalityAccess the plugin settings or admin pages for Photo Gallery Builder. Look for features that modify galleries, upload media, change plugin settings, or manage other users. Test whether these functions are accessible without explicit admin capability checks.Affected if The plugin exposes administrative functions (gallery management, settings modification, media handling) that do not require Administrator role verification.
-
Inspect capability requirementsIf you have access to the plugin source code, examine the callback functions for admin actions. Look for calls to current_user_can() or related WordPress capability checks. Note any functions missing these checks.Affected if Plugin functions that should require Administrator capabilities (like managing galleries, modifying settings) lack proper current_user_can() verification.
Your environment is affected if Wpdiscover Photo Gallery Builder version 3.0 or lower is installed AND non-Administrator users can access or execute administrative functions within the plugin.
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 Photo Gallery Builder to the latest version which should include proper authorization checks. If no update is available, restrict access to affected endpoints and audit plugin functionality for additional access control issues.
Fix this in Photo Gallery Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49325 — 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-2024-49325 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