dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-57395

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

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 Themefic Tourfic tourfic allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Tourfic: from n/a through <= 2.22.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 confidence

The Themefic Tourfic WordPress plugin has a missing authorization vulnerability allowing exploitation of incorrectly configured access control security levels. An authenticated user can likely perform actions or access resources beyond their intended permission level due to insufficient authorization checks in the plugin's functionality.

MitigationImplement proper authorization verification checks at each sensitive function entry point, ensuring user permissions are validated before executing privileged operations. Update to the latest patched version if available.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Verify Tourfic plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Tourfic' or 'Themefic Tourfic'. Alternatively, check via file system: look for /wp-content/plugins/tourfic/ directory.
    Affected if The Tourfic plugin is installed and active on the WordPress site.
  2. Identify installed Tourfic version
    In WordPress admin, go to Plugins > Installed Plugins > Tourfic and note the version number displayed. Alternatively, check the plugin's main PHP file header or readme.txt for the Version field.
    Affected if The installed version is older than the current patched version released for this CVE.
  3. Review user role and capability settings
    Go to Users > Roles in WordPress admin, or use a role management plugin to review what capabilities are assigned to roles below Administrator. Check if Tourfic-specific capabilities (e.g., tourfic_manage_options, tourfic_settings) are incorrectly assigned to Editor, Author, or Contributor roles.
    Affected if Non-administrator users have elevated Tourfic capabilities that should be restricted to administrators only.
  4. Inspect Tourfic plugin settings for access control
    Navigate to Tourfic settings pages in WordPress admin (usually under Tourfic menu). Look for any settings related to user access, permission levels, or security configuration that may be misconfigured.
    Affected if Settings allow authenticated users to access administrative-level Tourfic functions or data.
  5. Test for authorization bypass
    Using a lower-privilege user account (e.g., Editor), attempt to access Tourfic administrative functions directly via URL or make API calls to Tourfic endpoints that should require administrator privileges.
    Affected if A non-administrator authenticated user can successfully access or modify Tourfic settings or data that should require administrator-level authorization.

You are affected if the Tourfic plugin is installed and either the version is unpatched OR non-administrator users can access administrative-level Tourfic functions due to missing authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization verification checks at each sensitive function entry point, ensuring user permissions are validated before executing privileged operations. Update to the latest patched version if available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57395 — 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-2026-57395 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