Zephyr Project ManagerWordPress extension · Zephyr Project Manager Project
CVE-2023-34373
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 Dylan James Zephyr Project Manager plugin <= 3.3.93 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Zephyr Project Manager WordPress plugin versions 3.3.93 and below allows attackers to induce authenticated users to execute unwanted administrative actions by tricking them into visiting malicious pages.
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
Zephyr Project ManagerWordPress extension
<= 3.3.93CVSS 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.
-
Locate the Zephyr Project Manager plugin filesCheck your WordPress installation under wp-content/plugins/ for a folder named 'zephyr-project-manager' or similar variantAffected if The plugin folder exists in the plugins directory
-
Identify the installed versionOpen the main plugin file (usually named zephyr-project-manager.php) or readme.txt and locate the version number declared in the plugin headerAffected if The version listed is 3.3.93 or lower
-
Verify the plugin is activeLog into WordPress admin and navigate to Plugins > Installed Plugins, or query the wp_options table for the active_plugins option to check if Zephyr Project Manager is enabledAffected if The plugin appears in the list of active plugins or is present in active_plugins
-
Check for nonce verification in admin actionsIf you have access to the plugin source code, inspect PHP files handling admin form submissions (typically in includes/ or core/ folders) for the presence of wp_verify_nonce or check_admin_referer calls before any database write operationsAffected if State-changing admin functions lack nonce verification (the vulnerability condition)
-
Confirm WordPress user authenticationRecall that this CSRF vulnerability requires an authenticated administrator to inadvertently visit a malicious external page while logged inAffected if Administrative users with active sessions exist for this WordPress site
You are affected if the Zephyr Project Manager plugin is installed, active, and running version 3.3.93 or lower without CSRF token protection on admin actions.
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.
From vendor dataImplement anti-CSRF tokens (nonce verification) on all state-changing admin actions and forms within the plugin, and update to a patched version if available from the vendor.
Fix this in Zephyr Project Manager
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34373 — 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-2023-34373 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