Wp Social Feed GalleryWordPress extension · Quadlayers
CVE-2019-15779
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 insta-gallery plugin before 2.4.8 for WordPress has no nonce validation for qligg_dismiss_notice or qligg_form_item_delete.
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 insta-gallery WordPress plugin before version 2.4.8 lacks proper nonce validation on two AJAX action handlers (qligg_dismiss_notice and qligg_form_item_delete). This allows attackers to forge requests on behalf of authenticated administrators through CSRF attacks, potentially enabling unauthorized deletion of gallery items or dismissal of notices.
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
Wp Social Feed GalleryWordPress extension
< 2.4.8CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Check installed plugin versionNavigate to WordPress admin > Plugins > Insta Gallery (or Wp Social Feed Gallery) and view the version number, or inspect the main plugin file (e.g., insta-gallery/insta-gallery.php) to find the Version headerAffected if Version is below 2.4.8
-
Locate the AJAX action handlersExamine the plugin PHP files for functions handling 'qligg_dismiss_notice' and 'qligg_form_item_delete' AJAX actions, typically found in the main plugin file or an includes/ajax.php fileAffected if These AJAX handlers exist in the plugin code
-
Inspect nonce validation in AJAX handlersReview the code for the qligg_dismiss_notice and qligg_form_item_delete action handlers to check if they call wp_verify_nonce or check_admin_referer before processing the requestAffected if The handlers lack proper nonce validation (missing wp_verify_nonce or check_admin_referer calls)
-
Verify AJAX endpoints are accessibleTest accessing the AJAX endpoints via wp-admin/admin-ajax.php with action=qligg_dismiss_notice or action=qligg_form_item_delete, observing if requests are processed without a valid nonce parameterAffected if Requests are processed without requiring a valid nonce token
You are affected if the insta-gallery plugin version is below 2.4.8 AND the AJAX handlers for qligg_dismiss_notice or qligg_form_item_delete lack proper nonce validation, allowing CSRF attacks to delete gallery items or dismiss notices on behalf of authenticated administrators.
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 data2.4.8
Update the insta-gallery plugin to version 2.4.8 or later which implements proper nonce validation for the affected AJAX endpoints.
Fix this in Wp Social Feed 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-2019-15779 — 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-2019-15779 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