dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67573

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in ThimPress Sailing sailing allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Sailing: from n/a through < 4.4.6.

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 confidence

The ThimPress Sailing theme/plugin for WordPress has a missing authorization vulnerability where certain functions or endpoints lack proper access control checks. This allows unauthenticated or lower-privilege users to access functionality intended for higher-privilege users due to incorrectly configured access control security levels.

MitigationUpgrade to Sailing version 4.4.6 or later. Alternatively, review the codebase for functions lacking capability checks, nonce verification, and role-based access control enforcement, then add proper authorization checks to all sensitive operations.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ThimPress Sailing installation
    Check if the Sailing theme or plugin is installed on the WordPress site by examining the wp-content/themes or wp-content/plugins directory for 'sailing' or 'thimpress' folders. Alternatively, look for the theme/plugin in WordPress admin under Appearance > Themes or Plugins > Installed Plugins.
    Affected if The Sailing theme or plugin from ThimPress is present on the WordPress site.
  2. Determine installed version
    For theme: Check the style.css file in the theme directory for the 'Version:' header. For plugin: Check the main plugin PHP file for the 'Version:' header in the plugin comment block. Compare this version number to 4.4.6.
    Affected if The installed version is lower than 4.4.6.
  3. Inspect functions lacking capability checks
    Review the theme/plugin PHP files, particularly in includes/ or classes/ directories, for sensitive functions such as AJAX handlers, admin_init hooks, or custom endpoints. Search for functions that perform sensitive operations (database modifications, settings changes, user management) without calling current_user_can(), check_admin_referer(), or similar authorization functions.
    Affected if Sensitive functions are found that do not contain capability checks (current_user_can) or nonce verification (wp_verify_nonce/check_admin_referer).
  4. Test for unauthorized access to admin functions
    Use a tool like curl or Burp Suite to send requests to known admin-action endpoints (such as wp-admin/admin-ajax.php?action=thim_*) without authenticating or with a low-privilege user account. Observe if the requests succeed and return sensitive data or perform privileged actions.
    Affected if Requests to admin functions succeed without proper authentication or authorization validation.

The environment is affected if the ThimPress Sailing theme/plugin is installed with a version lower than 4.4.6 and sensitive functions or endpoints are accessible without proper capability checks or authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Sailing version 4.4.6 or later. Alternatively, review the codebase for functions lacking capability checks, nonce verification, and role-based access control enforcement, then add proper authorization checks to all sensitive operations.

Recommended fix Moderate confidence

4.4.6 or later

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Appearance > Themes (if Sailing is a theme) or Plugins (if Sailing is a plugin)
  4. 4. Locate the ThimPress Sailing theme/plugin
  5. 5. Check the current version to confirm it is below 4.4.6
  6. 6. Update ThimPress Sailing to version 4.4.6 or later
  7. 7. Verify the update was successful by checking the version number
  8. 8. Test the access control functionality to confirm the authorization vulnerability is remediated
Caveat Review the theme/plugin changelog for any potential breaking changes between your current version and 4.4.6

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67573 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67573 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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