Zephyr Project ManagerWordPress extension · Zephyr Project Manager Project
CVE-2023-31237
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 · uneditedURL Redirection to Untrusted Site ('Open Redirect') vulnerability in Dylan James Zephyr Project Manager.This issue affects Zephyr Project Manager: from n/a through 3.3.9.
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 confidenceOpen Redirect vulnerability in Zephyr Project Manager allows an attacker to craft a malicious URL that redirects users to an untrusted external site. The vulnerability exists in versions up to 3.3.9 and likely involves insufficient validation of redirect targets in the application's URL handling logic.
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.91CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Identify installed version of Zephyr Project ManagerLocate the version number in the application's about page, package.json, or installation metadata. Check the software inventory or software bill of materials (SBOM) if available.Affected if The installed version is any version prior to 3.3.91 (versions 3.3.9 and below)
-
Locate redirect functionality in the applicationSearch the application's source code or configuration for URL redirection logic. Look for functions handling 'redirect', 'returnUrl', 'next', 'target', or similar parameters that control user navigation.Affected if The application contains any redirect handling logic that processes user-supplied input
-
Inspect redirect parameter handling for external URLsExamine the code handling redirect destinations. Determine if parameters accepting redirect URLs allow absolute/external URLs (http://, https://) or only relative paths.Affected if The redirect logic accepts user input without restricting to relative paths or an allowlist of trusted domains
-
Test redirect parameters with external URLs (if authorized)If you have a test environment, craft a request with an external domain in the redirect parameter (e.g., ?redirect=https://malicious-site.com) and observe if the application redirects to that external URL.Affected if The application redirects to any user-controlled external domain without validation
You are affected if Zephyr Project Manager version is below 3.3.91 AND the application exposes any redirect functionality that does not validate that redirect targets are relative or restricted to trusted domains.
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 · scoped3.3.91
Implement strict validation of redirect URLs to ensure they are relative or point to trusted domains only; avoid allowing user-controlled input to dictate redirect destinations without proper allowlist validation.
3.3.91 or later
- Upgrade Zephyr Project Manager to version 3.3.91 or later
Generated from the published advisory — verify against the referenced sources before acting.
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-31237 — 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-31237 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