dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-6721

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-19
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
The Vchasno Kasa plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the mrkv_vchasno_kasa_wc_do_metabox_action() function in all versions up to, and including, 1.0.3. This makes it possible for unauthenticated attackers to generate invoices for arbitrary orders.

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 · high confidence

The Vchasno Kasa WordPress plugin lacks a capability check on the mrkv_vchasno_kasa_wc_do_metabox_action() function, allowing unauthenticated users to trigger invoice generation for arbitrary orders by making direct requests to the affected endpoint.

MitigationUpdate the plugin to version 1.0.4 or later once available, which should include proper capability checks and nonce verification on the vulnerable function.

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 Vchasno Kasa plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Vchasno Kasa' or check the wp-content/plugins directory for a folder containing 'vchasno-kasa'
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    In WordPress admin plugins list, click on the plugin to view version details, or open the main plugin PHP file and look for the Version header in the plugin comment block
    Affected if Version is lower than 1.0.4 or the version cannot be determined (unknown)
  3. Confirm vulnerable function exists
    Inspect the plugin files (typically in the main PHP file or includes) for the function mrkv_vchasno_kasa_wc_do_metabox_action() - search for 'add_action' hooks referencing this function
    Affected if The function exists and is hooked via wp_ajax or wp_ajax_nopriv (allowing unauthenticated access)
  4. Test endpoint accessibility without authentication
    Make a direct POST request to the WordPress AJAX endpoint (wp-admin/admin-ajax.php) with action=mrkv_vchasno_kasa_wc_do_metabox_action and an order_id parameter, without providing any authentication tokens or nonces
    Affected if The request is processed without returning an authentication or capability error (response does not contain 403, 'permission denied', or 'cheating' errors)
  5. Check for recent admin activity logs
    Review WordPress audit logs or security plugins for any suspicious invoice generation events on orders you did not initiate, or check the order notes/history for unexpected invoice generation
    Affected if Invoice generation events exist for orders you did not create or authorize

If the Vchasno Kasa plugin is installed with a version before 1.0.4 AND the vulnerable function is hooked without capability checks (visible via wp_ajax_nopriv), the environment is affected by this CVE.

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

Update the plugin to version 1.0.4 or later once available, which should include proper capability checks and nonce verification on the vulnerable function.

Recommended fix Moderate confidence

Version higher than 1.0.4 (check WordPress plugin repository for latest fixed release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Vchasno Kasa' plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, manually download the updated plugin from the WordPress plugin repository and reinstall
Caveat Review plugin changelog for any breaking changes before updating in production environments

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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