CVE-2025-22737
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 · uneditedMissing Authorization vulnerability in magepeopleteam WpTravelly tour-booking-manager allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WpTravelly: from n/a through <= 1.8.5.
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 confidenceMissing authorization in the WpTravelly WordPress plugin allows users to access functionality that should be restricted by Access Control Lists (ACLs). This means unauthenticated or lower-privileged users can potentially reach admin-level functions due to improper capability checks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Confirm WpTravelly plugin is installedLog into WordPress admin dashboard, navigate to Plugins > Installed Plugins. Search for 'WpTravelly' in the plugin list.Affected if The WpTravelly plugin appears in the installed plugins list and is activated
-
Identify installed plugin versionIn the Plugins list, click on the WpTravelly plugin to expand details, or access the plugin file header via FTP/file manager at wp-content/plugins/wptravelly/wptravelly.php to read the Version header.Affected if The installed version matches the vulnerable version range for this CVE
-
Check for exposed admin endpointsUse a browser or HTTP tool to access WpTravelly plugin URLs (such as admin action parameters like ?action=wptravelly_*, ?page=wptravelly*, or AJAX endpoints under wp-admin/admin-ajax.php?action=wptravelly*) without proper authentication.Affected if Requests to these endpoints return success or admin-level data without requiring login or proper capability verification
-
Verify capability check implementationAccess the plugin PHP files via FTP or file manager. Search for sensitive functions (settings updates, booking modifications, user data access) and verify they include current_user_can() or similar WordPress capability checks before execution.Affected if Sensitive functions lack proper current_user_can() or role-based capability checks
If WpTravelly is active and the installed version falls within the affected range, the environment may allow unauthorized access to privileged plugin functions due to missing authorization checks.
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 proper capability checks and role-based access controls on all sensitive functions within the plugin, ensuring only authorized user roles can execute privileged operations.
- 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-2025-22737 — 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-2025-22737 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