Photo GalleryWordPress extension · 10web
CVE-2017-12977
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 Web-Dorado "Photo Gallery by WD - Responsive Photo Gallery" plugin before 1.3.51 for WordPress has a SQL injection vulnerability related to bwg_edit_tag() in photo-gallery.php and edit_tag() in admin/controllers/BWGControllerTags_bwg.php. It is exploitable by administrators via the tag_id parameter.
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 confidenceSQL injection vulnerability in the WordPress 'Photo Gallery by WD' plugin affecting the tag_id parameter in bwg_edit_tag() and edit_tag() functions. Exploitation requires administrative privileges, allowing attackers with admin access to inject malicious SQL queries through the vulnerable parameter.
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 GalleryWordPress extension
<= 1.3.50CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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.
-
Identify installed Photo Gallery by WD plugin versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate 'Photo Gallery by WD' or '10web Photo Gallery' and read the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file header for the Version constant.Affected if The installed version is 1.3.50 or lower.
-
Confirm plugin is activeIn the WordPress Plugins admin page, verify that Photo Gallery by WD shows as 'Active' under the plugin status. Only the active plugin code would be executed.Affected if The plugin is installed and active.
-
Locate vulnerable function filesAccess the WordPress file system via FTP or file manager. Navigate to wp-content/plugins/photo-gallery-by-wd/ and locate files containing 'bwg_edit_tag' or 'edit_tag' functions, typically in admin/models/ or similar directory structure.Affected if The files bwg_edit_tag.php or related tag editing files exist in the plugin directory.
-
Check tag_id parameter handlingExamine the identified tag edit PHP files for code that directly uses the tag_id parameter in SQL queries without proper sanitization or prepared statements. Look for patterns like 'WHERE tag_id = ' . $_POST['tag_id'] or similar unsanitized usage.Affected if The code directly incorporates the tag_id parameter into SQL queries without escaping or prepared statements.
You are affected if Photo Gallery by WD plugin version 1.3.50 or lower is active and the vulnerable tag editing functions exist with unsanitized tag_id parameter handling.
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 Photo Gallery by WD plugin to version 1.3.51 or later. Since exploitation requires admin-level access, also review admin accounts for compromise and implement least-privilege admin policies.
Fix this in Photo Gallery
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12977 — 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-2017-12977 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