dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-13833

HIGH · 7.2 CVSS v3.1 Published 2025-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
The Album Gallery – WordPress Gallery plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.6.3 via deserialization of untrusted input from gallery meta. This makes it possible for authenticated attackers, with Editor-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 · high confidence

The Album Gallery WordPress plugin up to version 1.6.3 is vulnerable to PHP Object Injection via unsafe deserialization of gallery metadata. Authenticated attackers with Editor-level access or higher can inject arbitrary PHP objects. While the plugin itself lacks a POP chain, the vulnerability becomes exploitable when combined with other plugins or themes containing a POP chain, potentially allowing arbitrary file deletion, data retrieval, or code execution.

MitigationUpdate the Album Gallery plugin to a version beyond 1.6.3. Additionally, audit all installed plugins and themes for known POP chains, and limit Editor-level access until the update is applied.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Album Gallery plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Album Gallery' or 'Album Gallery - Photo Gallery and Music Player' in the list. Note the version number displayed.
    Affected if The plugin is listed and the version is 1.6.3 or lower, or no version is shown but the plugin name matches.
  2. Confirm the installed version against affected range
    Compare the version shown in the plugins list to 1.6.3. The plugin version is typically displayed beneath the plugin name in the format 'Version: X.X.X'.
    Affected if The installed version is 1.6.3 or any version lower than 1.6.3.
  3. Identify users with Editor-level access
    In WordPress admin, go to Users > All Users and review the Role column. Count users assigned the 'Editor' role or any role with higher privileges (Administrator, Super Admin).
    Affected if There is at least one user account with Editor-level access or higher in the WordPress installation.
  4. Check if gallery functionality is in active use
    Look for any published posts, pages, or custom post types that contain Album Gallery shortcodes (such as [album_gallery] or similar patterns) or check if any galleries have been created using the plugin.
    Affected if Galleries have been created or the plugin's shortcodes appear in published content, indicating the vulnerable metadata deserialization could be triggered.
  5. Audit for plugins with known POP chains
    Review the list of all installed plugins (Plugins > Installed Plugins) and note any that are known to contain POP chain gadgets. Common examples include plugins with vulnerable versions of serialization functions or known unserialize() vulnerabilities.
    Affected if Any other installed plugin or theme contains a POP chain gadget that could be combined with the Album Gallery vulnerability for code execution.

A user is affected if the Album Gallery plugin version is 1.6.3 or lower AND there are users with Editor-level access or higher, regardless of whether the plugin is actively used for galleries.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Album Gallery plugin to a version beyond 1.6.3. Additionally, audit all installed plugins and themes for known POP chains, and limit Editor-level access until the update is applied.

Recommended fix Moderate confidence

Album Gallery plugin version 1.6.4 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Album Gallery plugin
  4. Check if current version is 1.6.3 or below
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/album-gallery and upload via Plugins > Add New > Upload Plugin

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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 locally
dbcve dependency scanner

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