dbcve.org
VimeographyWordPress extension · Davekiss

CVE-2024-0825

HIGH · 8.8 CVSS v3.1 Published 2024-03-05
Fix available
A fix is available. Upgrade to 2.3.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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 Vimeography: Vimeo Video Gallery WordPress Plugin plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.3.2 via deserialization of untrusted input via the vimeography_duplicate_gallery_serialized in the duplicate_gallery function. This makes it possible for authenticated attackers attackers, with contributor access or higher, to inject a PHP Object. No POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

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 Vimeography WordPress plugin up to version 2.3.2 is vulnerable to PHP Object Injection via the vimeography_duplicate_gallery_serialized parameter in the duplicate_gallery function. The plugin deserializes untrusted input without proper validation, allowing authenticated attackers with contributor-level access or higher to inject arbitrary PHP objects. While no POP chain exists within the plugin itself, a POP chain from another installed plugin or theme could enable remote code execution, arbitrary file deletion, or sensitive data access.

MitigationUpdate to version 2.3.3 or later. If no update is available, disable the plugin until a patch is released. Alternatively, implement strict input validation and replace unsafe unserialize() calls with json_decode() or other safer deserialization methods.

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
VimeographyWordPress extension
Affected:< 2.3.3

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate the Vimeography plugin installation
    Navigate to WordPress admin > Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'vimeography'
    Affected if The plugin folder exists in the WordPress installation
  2. Determine the installed Vimeography version
    Check the plugin header in the main plugin file (usually vimeography.php) for the 'Version' field, or view the version number in the WordPress plugins list
    Affected if The version number is less than 2.3.3 (e.g., 2.3.2, 2.3.1, 2.3.0, etc.)
  3. Inspect the duplicate_gallery function
    Access the plugin source code and locate the duplicate_gallery function (typically in includes/class-vimeography.php or similar). Look for use of unserialize() on the vimeography_duplicate_gallery_serialized parameter
    Affected if The function contains an unserialize() call processing the vimeography_duplicate_gallery_serialized POST/GET parameter without validation
  4. Verify WordPress user roles with access
    Review the capability check in the duplicate_gallery function (look for 'contributor' or higher role requirement using current_user_can() or similar)
    Affected if The function allows contributor-level users (not just administrators) to access the vulnerable endpoint
  5. Test for POP chain availability
    Audit other active plugins and themes for classes with magic methods (__wakeup, __destruct, __toString, __get) that could form a POP chain usable with this injection point
    Affected if Other installed plugins or themes contain exploitable POP chain classes alongside the vulnerable Vimeography version

A user is affected if the Vimeography plugin version is below 2.3.3 and the duplicate_gallery function with unsafe unserialize() is present and accessible to contributor-level users.

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
Upgrade available Upgrade to 2.3.3 or later
Fixed in 2.3.3
Interim mitigation

Update to version 2.3.3 or later. If no update is available, disable the plugin until a patch is released. Alternatively, implement strict input validation and replace unsafe unserialize() calls with json_decode() or other safer deserialization methods.

Recommended fix High confidence

Vimeography: Vimeo Video Gallery version 2.3.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Vimeography: Vimeo Video Gallery
  4. Check if current version is less than 2.3.3
  5. If vulnerable, click 'Update Now' to upgrade to version 2.3.3
  6. Verify the update completed successfully

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

Fix this in Vimeography Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

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