CVE-2026-5347
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 HM Books Gallery plugin for WordPress is vulnerable to Missing Authorization in versions up to and including 4.8.0. This is due to the absence of capability checks and nonce verification in the admin_init hook that handles the permalink settings update at line 205-209 of wp-books-gallery.php. The vulnerable code checks only for the presence of the 'permalink_structure' POST parameter before updating the 'wbg_cpt_slug' option, without verifying that the request comes from an authenticated administrator. This makes it possible for unauthenticated attackers to modify the custom post type slug for the books gallery, which changes the URL structure for all book entries and can break existing links and SEO rankings.
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 HM Books Gallery WordPress plugin lacks authorization checks in its admin_init hook (wp-books-gallery.php lines 205-209), allowing any unauthenticated request to modify the 'wbg_cpt_slug' option by simply including a 'permalink_structure' POST parameter. This enables attackers to change the custom post type slug, breaking existing book entry URLs and harming SEO.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Check if HM Books Gallery plugin is installedNavigate to WordPress admin > Plugins and look for 'HM Books Gallery' or check the plugins directory at /wp-content/plugins/ for a folder starting with 'hm-books-gallery' or similar. Check the plugin header in the main PHP file for the version number.Affected if The plugin is installed and active, regardless of version (no fixed version has been confirmed)
-
Locate the vulnerable admin_init hookOpen the plugin file wp-books-gallery.php and locate lines 205-209, or search for 'admin_init' hook and 'wbg_cpt_slug' option handling. Look for code that processes a 'permalink_structure' POST parameter without checking user capabilities or nonces.Affected if The file contains an admin_init hook that processes 'permalink_structure' POST parameter to update 'wbg_cpt_slug' without authorization checks (no current_user_capability or wp_verify_nonce)
-
Inspect current wbg_cpt_slug option valueAccess the WordPress database (via phpMyAdmin or wp-cli: wp option get wbg_cpt_slug) or check the plugin settings page in admin. Look for the current custom post type slug configuration.Affected if The option exists and contains a value (indicating the plugin is configured and the vulnerability could alter this value)
-
Verify lack of authorization in the option update logicIn wp-books-gallery.php around lines 205-209, confirm that the code handling the POST parameter does NOT include: current_user_can('manage_options'), wp_verify_nonce, check_admin_referer, or any capability check before updating the wbg_cpt_slug option.Affected if The code updates the option without any authorization check, allowing unauthenticated attackers to modify it
You are affected if the HM Books Gallery plugin is installed and its wp-books-gallery.php file contains the vulnerable admin_init hook (lines 205-209) that processes 'permalink_structure' without authorization, regardless of the current option value.
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.
dbcve · scopedApply vendor patch when available; until then, consider disabling the plugin or adding a temporary web application firewall rule to block requests to the affected admin_init endpoint.
4.8.1 or later
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the 'HM Books Gallery' plugin
- Check if an update to version 4.8.1 or later is available
- If available, click 'Update Now' to install the patched version
- If no update is available through the WordPress admin, download version 4.8.1 or later from the official WordPress plugin repository at plugins.trac.wordpress.org/plugin/hm-books-gallery
- Deactivate and delete the current vulnerable version, then upload and install the fixed version
- Verify the plugin is functioning correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5347 — 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-2026-5347 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