CVE-2026-9829
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 Photo Gallery by 10Web – Mobile-Friendly Image Gallery plugin for WordPress is vulnerable to time-based SQL Injection via 'compact_album_order_by' Shortcode Parameter in all versions up to, and including, 1.8.41 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The malicious payload is stored via the 'shortcode_bwg' AJAX handler — accessible to Contributor-level users and exploitable without a valid nonce by omitting the 'page' parameter — and is subsequently triggered by the unauthenticated 'bwg_frontend_data' AJAX handler, meaning successful exploitation requires only that an attacker has Contributor-level access to save the shortcode.
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 confidenceTime-based SQL injection vulnerability in the Photo Gallery by 10Web WordPress plugin allows authenticated attackers with Contributor-level access to inject malicious SQL via the 'compact_album_order_by' shortcode parameter. The payload is stored through the 'shortcode_bwg' AJAX handler (exploitable without a valid nonce by omitting the 'page' parameter) and triggered when the unauthenticated 'bwg_frontend_data' AJAX handler processes it, enabling extraction of sensitive database information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify Photo Gallery by 10Web plugin is installedCheck for the plugin directory at wp-content/plugins/photo-gallery-by-10web/ or list all installed plugins via wp-admin/plugins.phpAffected if The plugin directory exists and the plugin is active
-
Check installed plugin versionOpen wp-content/plugins/photo-gallery-by-10web/photo-gallery.php and locate the Version header in the plugin comment block, or check the version listed on the Plugins page in wp-adminAffected if Version is 1.8.41 or lower (versions newer than 1.8.41 are patched)
-
Confirm AJAX endpoint accessibilityVerify that the shortcode_bwg and bwg_frontend_data AJAX endpoints are accessible by checking if the files exist at wp-admin/admin-ajax.php?action=shortcode_bwg and wp-admin/admin-ajax.php?action=bwg_frontend_data, or inspect the plugin PHP files for these action hooksAffected if The AJAX handlers are registered and publicly accessible
-
Check for Contributor-level user accountsNavigate to wp-admin/users.php and review the user list, or query the wp_users table for users with the Contributor roleAffected if Any Contributor-level accounts exist in the system
-
Inspect server logs for suspicious SQL patternsReview web server access logs (apache2/access.log, nginx/access.log) or WordPress debug logs for requests containing SQL injection patterns such as UNION SELECT, OR 1=1, or common SQL keywords in the compact_album_order_by parameterAffected if Recent requests contain SQL injection payloads targeting the bwg_frontend_data or shortcode_bwg actions
The environment is affected if the Photo Gallery by 10Web plugin version is 1.8.41 or lower, the plugin is active, and Contributor-level users exist or suspicious SQL injection attempts are logged against the vulnerable AJAX handlers.
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 10Web plugin to a version newer than 1.8.41. Until patched, restrict or audit Contributor-level users who can create or modify gallery shortcodes.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9829 — 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 sources- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- www.wordfence.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9829 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