dbcve.org
Photo GalleryWordPress extension · Ays Pro

CVE-2016-10921

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 1.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The gallery-photo-gallery plugin before 1.0.1 for WordPress has SQL injection.

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 confidence

SQL injection vulnerability in the gallery-photo-gallery WordPress plugin affecting versions prior to 1.0.1. The vulnerability allows attackers to inject malicious SQL queries through unsanitized input within the plugin's functionality.

MitigationUpdate the gallery-photo-gallery plugin to version 1.0.1 or later. If immediate update is not possible, consider disabling the plugin until the patch can be applied.

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
Affected:< 1.0.1

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Ays Pro Photo Gallery' or 'gallery-photo-gallery' in the plugin list.
    Affected if The plugin appears in the installed plugins list
  2. Check installed version
    In the plugins list, click on the plugin to view details, or check the plugin header file (typically in wp-content/plugins/gallery-photo-gallery/readme.txt or readme.md) for the version number.
    Affected if The version number is below 1.0.1 (for example: 1.0.0, 0.9.x, etc.)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the plugin status shows 'Active' under the plugin name.
    Affected if The plugin is currently activated and the version is below 1.0.1
  4. Review access logs for SQL injection attempts
    Check web server access logs (Apache error.log, Nginx access.log) or WordPress security logs for unusual SQL syntax in requests to /wp-admin/admin-ajax.php or plugin endpoints containing 'gallery-photo-gallery' in the URL.
    Affected if Logs show SQL injection patterns (UNION SELECT, OR 1=1, etc.) targeting the plugin endpoints

You are affected if the Ays Pro Photo Gallery plugin is installed, active, and the version is below 1.0.1, making unsanitized SQL input exploitable through the plugin's functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.1 or later
Fixed in 1.0.1
Interim mitigation

Update the gallery-photo-gallery plugin to version 1.0.1 or later. If immediate update is not possible, consider disabling the plugin until the patch can be applied.

Recommended fix High confidence

Photo Gallery plugin version 1.0.1 or latest stable release

  1. Back up your WordPress site database and files before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find the 'Photo Gallery' plugin and click 'Update now' or update to version 1.0.1 or latest available
  4. Alternatively, you can update via FTP by downloading the latest version from wordpress.org/plugins/gallery-photo-gallery/ and uploading to wp-content/plugins/
  5. After updating, verify the plugin version is 1.0.1 or higher in the plugins list
  6. Test that the gallery functionality works correctly after the update
Caveat Review plugin settings after upgrade as minor configuration changes may occur between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Photo Gallery Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10921 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10921 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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