CVE-2022-30706
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 · uneditedOpen redirect vulnerability in Booked versions prior to 3.3 allows a remote unauthenticated attacker to redirect a user to an arbitrary web site and conduct a phishing attack by having a user to access a specially crafted URL.
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 confidenceOpen redirect vulnerability in Booked application allows unauthenticated remote attackers to craft malicious URLs that redirect users to arbitrary external websites. The vulnerability exists in versions prior to 3.3 due to insufficient validation of redirect parameters, enabling phishing attacks.
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< 3.3.0CVSS 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 the installed Booked versionLocate the version file or check the admin dashboard footer for the current version number. Common locations include a version.php file in the installation directory or the 'About' section in the admin panel.Affected if The installed version is lower than 3.3.0 (e.g., 3.2.x, 3.1.x, earlier versions)
-
Verify unauthenticated access is possibleDetermine if the Booked application is accessible without login. Attempt to access the login page and public-facing reservation pages without authenticating.Affected if The application allows unauthenticated access to pages that accept redirect parameters
-
Inspect redirect parameter handlingReview the application source code or configuration for how redirect parameters (such as 'returnUrl', 'redirect', 'url', or similar) are processed. Look for validation logic that should restrict redirects to trusted internal paths.Affected if The application accepts redirect parameters without strict validation against an allowlist of internal paths, or validation is missing entirely
-
Test for open redirect vulnerabilityCraft a test URL with a redirect parameter pointing to an external domain (e.g., https://example.com) and observe if the application redirects there without warning or validation message.Affected if The application redirects to the arbitrary external URL specified in the parameter without validating it is an internal path
Your environment is affected if Booked version is below 3.3.0 and the application processes redirect parameters without validating they point only to trusted internal paths.
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.0
Upgrade Booked to version 3.3 or later which contains the security patch. If immediate upgrade is not possible, implement input validation on redirect parameters to ensure only trusted internal paths are allowed.
3.3.0
- 1. Back up your current Booked installation and database before upgrading.
- 2. Download Booked version 3.3.0 or later from the official repository (www.bookedscheduler.com).
- 3. Review the upgrade instructions provided in the release notes.
- 4. Upload and extract the new version files to your server, replacing the existing installation.
- 5. Run any database migration scripts included in the upgrade package.
- 6. Verify the installation by logging in and testing the application functionality.
- 7. Test that the open redirect vulnerability is no longer present by attempting to access a crafted URL with a redirect parameter.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30706 — 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-2022-30706 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