dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-22343

HIGH · 8.6 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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
Unauthenticated Broken Access Control in WordPress Dating Theme <= 11.2.0 versions.

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

Unauthenticated Broken Access Control vulnerability in WordPress Dating Theme versions 11.2.0 and below allows unauthenticated attackers to bypass authorization checks and access functionality or data that should require authentication.

MitigationUpdate WordPress Dating Theme to patched version if available; otherwise implement proper capability checks and authentication verification on all sensitive endpoints.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

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

  1. Identify WordPress Dating Theme installation
    Locate the theme directory in wp-content/themes/ and check for a dating-themed theme folder (commonly 'dating-theme', 'sweetdate', or similar naming). List all installed themes via: ls -la wp-content/themes/
    Affected if WordPress Dating Theme is present in the themes directory
  2. Retrieve installed theme version
    Open the theme's style.css file (e.g., wp-content/themes/dating-theme/style.css) and locate the 'Version:' header in the comment block at the top of the file
    Affected if Version number is 11.2.0 or lower, or if no version is declared and the theme is confirmed as the Dating Theme
  3. Compare version to affected range
    Parse the version number found in style.css and compare against 11.2.0 using standard version comparison
    Affected if The installed version is 11.2.0 or below (e.g., 11.2.0, 11.1.0, 10.5.0, etc.)
  4. Test for unauthenticated access to sensitive endpoints
    Attempt to access common Dating Theme admin or user management endpoints without providing authentication credentials. Common paths include /wp-admin/admin-ajax.php, /wp-json/ endpoints, or theme-specific AJAX handlers. Use a browser or curl to send requests without cookies or authentication headers
    Affected if Requests to sensitive endpoints return successful responses (HTTP 200) rather than redirects to login (HTTP 302 to wp-login.php) or 401/403 errors

You are affected if the WordPress Dating Theme is installed with version 11.2.0 or below and sensitive endpoints are accessible without 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.

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

Update WordPress Dating Theme to patched version if available; otherwise implement proper capability checks and authentication verification on all sensitive endpoints.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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