dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-39543

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-08
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 Themefic Tourfic tourfic allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Tourfic: from n/a through <= 2.21.4.

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

Missing authorization vulnerability in the Themefic Tourfic WordPress plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly verify user permissions before allowing access to certain functionality, potentially permitting lower-privileged users to perform actions intended for higher-privilege roles.

MitigationImplement proper authorization checks (capability verification and nonce validation) on all sensitive functions and update to the patched version once released. Audit existing access control configurations.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 check wp-content/plugins/ directory for tourfic folder
    Affected if Tourfic plugin is not present in the WordPress installation
  2. Identify installed Tourfic version
    Check the plugin file header in wp-content/plugins/tourfic/tourfic.php or view the plugin details in WordPress admin Plugins page
    Affected if Unable to confirm version or version is unknown (compare to any known affected versions when available)
  3. Check for active user accounts with limited roles
    In WordPress admin, go to Users > All Users and review the roles assigned (Subscriber, Contributor, Author, Editor, etc.)
    Affected if There are users with roles below Administrator AND Tourfic plugin is installed
  4. Test unauthorized access to Tourfic admin functions
    Log in as a low-privilege user (e.g., Subscriber or Contributor) and attempt to access Tourfic-specific admin pages or AJAX endpoints (e.g., wp-admin/admin.php?page=tourfic, wp-admin/admin-ajax.php?action=tf_*)
    Affected if Low-privilege authenticated users can view or modify Tourfic settings or booking data they should not have access to
  5. Review Tourfic capability settings
    Inspect Tourfic plugin code for capability checks on sensitive functions - look for current_user_can() calls and compare required capabilities vs. actual assigned roles in wp-content/plugins/tourfic/
    Affected if Sensitive Tourfic functions lack proper current_user_can() checks or accept lower capability requirements than expected (e.g., using 'read' instead of 'manage_options')

A user is affected if Tourfic plugin is installed and any authenticated user with limited role (non-Administrator) can access Tourfic administrative functions, booking data, or settings that should require higher privileges.

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

Implement proper authorization checks (capability verification and nonce validation) on all sensitive functions and update to the patched version once released. Audit existing access control configurations.

Recommended fix Moderate confidence

Update to the latest available version of Tourfic (version newer than 2.21.4)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate the Tourfic plugin in the list
  4. 4. Check if an update is available for the Tourfic plugin
  5. 5. If an update is available, update to the latest version of Tourfic that is newer than 2.21.4
  6. 6. After updating, verify that the plugin functions correctly on your site
  7. 7. Test the authorization controls that were vulnerable to ensure the fix is working properly
Caveat Review the plugin changelog for any breaking changes between your current version and the new version before updating

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

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-39543 — 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-39543 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