VimeographyWordPress extension · Davekiss
CVE-2024-35770
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Dave Kiss Vimeography: Vimeo Video Gallery WordPress Plugin.This issue affects Vimeography: Vimeo Video Gallery WordPress Plugin: from n/a through 2.4.1.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in the Vimeography WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions, such as modifying gallery settings or configurations. This occurs because the plugin does not properly validate anti-CSRF tokens (nonces) on admin actions. The issue affects versions up to and including 2.4.1.
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
< 2.4.2CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Vimeography plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Vimeography' by Davekiss. Alternatively, check the /wp-content/plugins/ directory for a vimeography folder.Affected if The Vimeography plugin folder exists in the WordPress plugins directory
-
Identify installed versionIn WordPress admin, find Vimeography in the plugins list and check the version number displayed under the plugin name. Compare this to the affected range: versions before 2.4.2.Affected if Installed version is less than 2.4.2
-
Verify WordPress admin access existsCheck if the WordPress administrator dashboard (wp-admin) is accessible and in use. This CSRF vulnerability requires an authenticated administrator session to be targeted.Affected if Administrator accounts and wp-admin access exist in the environment
-
Inspect plugin for nonce validationExamine the main plugin PHP files (typically vimeography.php or files in /admin/ folder) for the presence of wp_nonce_field in forms and wp_verify_nonce or check_admin_referer in action handlers. Search for patterns like 'wp_create_nonce', 'wp_nonce_field', 'wp_verify_nonce', and 'check_admin_referer'.Affected if No nonce validation functions are found in admin action handlers, or admin forms lack nonce fields
Environment is affected if Vimeography plugin version is below 2.4.2 and the plugin handles admin actions without validating CSRF tokens (nonces).
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 · scoped2.4.2
Implement WordPress nonces (wp_nonce_field and wp_verify_nonce) on all admin-facing forms and action handlers within the plugin to verify the request originates from the legitimate admin session.
Vimeography: Vimeo Video Gallery version 2.4.2
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Vimeography: Vimeo Video Gallery' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 2.4.2 from the WordPress plugin repository
- Verify the plugin version shows 2.4.2 after updating
- Test that the Vimeo gallery functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Vimeography
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35770 — 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-35770 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