dbcve.org
Nextgen GalleryWordPress extension · Imagely

CVE-2019-14314

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-27
Fix available
A fix is available. Upgrade to 3.2.10 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
A SQL injection vulnerability exists in the Imagely NextGEN Gallery plugin before 3.2.11 for WordPress. Successful exploitation of this vulnerability would allow a remote attacker to execute arbitrary SQL commands on the affected system via modules/nextgen_gallery_display/package.module.nextgen_gallery_display.php.

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 confidence

A SQL injection vulnerability in the Imagely NextGEN Gallery WordPress plugin (versions before 3.2.11) allows remote attackers to execute arbitrary SQL commands through the nextgen_gallery_display module. The vulnerability stems from insufficient input sanitization in the affected PHP file, enabling attackers to manipulate SQL queries via crafted requests.

MitigationUpdate the NextGEN Gallery plugin to version 3.2.11 or later to remediate this vulnerability. As this is a critical (CVSS 9.8) SQL injection, immediate patching is recommended given the likelihood of active exploitation.

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
Nextgen GalleryWordPress extension
Affected:< 3.2.10

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. Identify if NextGEN Gallery plugin is installed
    In WordPress admin dashboard, navigate to Plugins > Installed Plugins and locate 'NextGEN Gallery' in the list. Note the version number displayed below the plugin name.
    Affected if Plugin is installed and version is less than 3.2.10 (or version shows 3.2.9 or earlier)
  2. Verify plugin version via filesystem
    If wp-admin access is unavailable, access the WordPress installation via FTP or file manager and locate the plugin version in /wp-content/plugins/nextgen-gallery/nextgen-gallery.php or the main plugin file header.
    Affected if Version header in the PHP file shows a version lower than 3.2.10
  3. Confirm nextgen_gallery_display module is in use
    Search WordPress posts, pages, and theme templates for the shortcode [nextgen_gallery] or the function call nggShowGallery() which invokes the nextgen_gallery_display module.
    Affected if The nextgen_gallery_display functionality is actively used on the site via shortcode or template inclusion
  4. Inspect the affected PHP file
    Locate the PHP file containing the nextgen_gallery_display module logic, typically in the /modules/ directory of the plugin. Examine the code for unsanitized user input being passed to SQL queries.
    Affected if The code contains direct SQL queries without prepared statements or proper input sanitization on parameters derived from user requests

You are affected if the NextGEN Gallery plugin is installed with a version below 3.2.10 and the nextgen_gallery_display module is in use on your site.

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 3.2.10 or later
Fixed in 3.2.10
Interim mitigation

Update the NextGEN Gallery plugin to version 3.2.11 or later to remediate this vulnerability. As this is a critical (CVSS 9.8) SQL injection, immediate patching is recommended given the likelihood of active exploitation.

Recommended fix High confidence

NextGEN Gallery version 3.2.11 or later

  1. 1. Backup the WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Locate the NextGEN Gallery plugin.
  5. 5. If automatic updates are enabled, the plugin may update automatically. If not, click 'Update Now' if an update is available.
  6. 6. Verify the plugin has been updated to version 3.2.11 or later.
  7. 7. Confirm the site still functions correctly after the update.

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

Fix this in Nextgen Gallery Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14314 — 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-2019-14314 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