CVE-2024-13906
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 Gallery by BestWebSoft – Customizable Image and Photo Galleries for WordPress plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 4.7.3 via deserialization of untrusted input in the 'import_gallery_from_csv' function. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.
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 confidenceThe Gallery by BestWebSoft plugin for WordPress is vulnerable to PHP Object Injection in the 'import_gallery_from_csv' function, which deserializes untrusted input without proper validation. Authenticated administrators can inject arbitrary PHP objects. While no POP chain exists in the plugin itself, if other installed plugins or themes contain POP chains, attackers could potentially achieve arbitrary code execution, file operations, or data exfiltration.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the Gallery by BestWebSoft plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Gallery by BestWebSoft', or inspect the /wp-content/plugins/gallery-plugin directoryAffected if The plugin is installed and active
-
Identify the installed plugin versionCheck the plugin main file (usually gallery-plugin.php) for the 'Version' header, or view the plugin details in the WordPress plugins pageAffected if The installed version falls within the vulnerable version range (compare against known affected versions)
-
Verify the import_gallery_from_csv function is accessibleCheck if the CSV import functionality is enabled in the plugin settings, typically under Gallery > Settings or a dedicated Import section in the admin dashboardAffected if The CSV import feature is enabled and accessible to administrator-level users
-
Confirm administrator-level user accounts existReview user accounts in WordPress admin under Users > All Users, focusing on those with Administrator roleAffected if At least one Administrator-level user account exists (required for the authenticated attack vector)
-
Inspect the vulnerable code pathExamine the plugin source file containing the import_gallery_from_csv function (typically in includes/admin or similar directory) for unserialize() calls on user-supplied CSV dataAffected if The code contains unserialize() processing of CSV import data without prior sanitization
A user is affected if they have the Gallery by BestWebSoft plugin installed with a vulnerable version, the CSV import feature is enabled, and administrator accounts exist on the WordPress site.
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 · scopedUpdate the plugin to the latest version when available. Until then, remove or disable the plugin if the CSV import functionality is not required, or restrict administrator access to trusted users only.
Gallery by BestWebSoft version 4.7.4 or later
- 1. Log in to the WordPress admin dashboard with Administrator-level credentials
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Gallery by BestWebSoft' in the plugin list
- 4. If an update is available, click 'Update Now' to update the plugin to the latest version
- 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
- 6. After updating, verify the plugin version is 4.7.4 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13906 — 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-2024-13906 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