dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14360

HIGH · 7.5 CVSS v3.1 Published 2026-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Kaira Blockons blockons allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Blockons: from n/a through <= 1.2.19.

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 Kaira Blockons WordPress plugin allows attackers to access functionality that should be restricted by Access Control Lists (ACLs). The plugin fails to properly validate user permissions before executing certain functions, enabling unauthenticated or unauthorized users to perform actions they should not have access to.

MitigationImplement proper authorization checks (capability verification, nonce validation, and ACL enforcement) on all sensitive functions in the plugin, and update to a patched version once released by the vendor.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Kaira Blockons plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Blockons' or 'Kaira Blockons' in the plugin list. Alternatively, check for the plugin directory at /wp-content/plugins/blockons/ or similar.
    Affected if The plugin appears in the installed plugins list and is activated
  2. Identify installed plugin version
    In the plugins list, click on the plugin name or view the plugin header file (usually blockons.php) to read the 'Version:' field in the plugin comment block.
    Affected if Version cannot be determined or is lower than the patched version released by the vendor
  3. Inspect plugin PHP files for authorization logic
    Examine the main plugin PHP files (blockons.php, admin/*.php) for function calls that handle AJAX actions, form submissions, or admin page access. Look for current_user_can(), wp_verify_nonce(), or capability checks like 'manage_options'.
    Affected if Sensitive functions lack capability checks or nonce validation before executing privileged operations
  4. Test non-authenticated access to admin functions
    If the plugin exposes AJAX endpoints (check wp_ajax_ and wp_ajax_nopriv_ hooks in the code), attempt to access them without logging in or providing credentials. Check if actions like saving settings, modifying content, or accessing restricted data succeed without authentication.
    Affected if AJAX or admin actions execute successfully without proper authentication or authorization
  5. Review user role and capability enforcement
    Create a test user with a limited role (e.g., Subscriber). While logged in as that user, attempt to access plugin functions that should require administrator privileges, such as plugin settings, content modification, or configuration changes.
    Affected if Limited-role users can perform actions that should be restricted to administrators

A user is affected if the Kaira Blockons plugin is installed and activated, lacks proper authorization checks on sensitive functions, or is running a version before the vendor's patched release.

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 checks (capability verification, nonce validation, and ACL enforcement) on all sensitive functions in the plugin, and update to a patched version once released by the vendor.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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