CVE-2025-31381
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 shiptrack Booking Calendar and Notification booking-calendar-and-notification allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Booking Calendar and Notification: from n/a through <= 4.0.3.
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 vulnerability in the shiptrack Booking Calendar and Notification WordPress plugin (versions <= 4.0.3) allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to booking management functions that should require proper authentication and authorization.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
-
Check if shiptrack Booking Calendar and Notification plugin is installedLocate the plugin directory at wp-content/plugins/ or access it via WordPress admin under Plugins > Installed Plugins. Look for 'shiptrack Booking Calendar and Notification' in the plugin list.Affected if The plugin appears in the installed plugins list
-
Identify the installed plugin versionIn WordPress admin, click on the plugin name to view its details, or inspect the main plugin file header in wp-content/plugins/shiptrack-booking-calendar-notification/ for the 'Version:' field.Affected if The version listed is 4.0.3 or lower
-
Confirm the plugin is activeIn WordPress admin under Plugins > Installed Plugins, check if the plugin shows as 'Active' - the vulnerability only affects actively running instances.Affected if The plugin status shows as Active alongside version 4.0.3 or lower
-
Review access control configuration for booking endpointsIf available, access the plugin settings panel to inspect any access control, permission, or role configuration options related to booking management functions.Affected if No role-based access restrictions are configured, or any user role can access booking management without explicit authorization checks
The environment is affected if the shiptrack Booking Calendar and Notification plugin is installed, active, and running version 4.0.3 or lower.
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 dataUpdate the Booking Calendar and Notification plugin to the latest version once available, and conduct a review of access control configurations to ensure all sensitive operations enforce proper authorization checks.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31381 — 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-31381 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