dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13666

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-06
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 Helloprint plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 2.1.2. This is due to the plugin registering a public REST API endpoint without implementing authorization checks to verify request authenticity. This makes it possible for unauthenticated attackers to arbitrarily modify WooCommerce order statuses via the /wp-json/helloprint/v1/complete_order_from_helloprint_callback endpoint by providing a valid order reference ID.

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 Helloprint WordPress plugin (versions up to 2.1.2) exposes a REST API endpoint at /wp-json/helloprint/v1/complete_order_from_helloprint_callback without any authorization checks. This allows unauthenticated attackers to modify WooCommerce order statuses by submitting valid order reference IDs, resulting in arbitrary order status changes.

MitigationAdd proper authorization and authentication checks to the REST API endpoint, such as a permission_callback verifying user capabilities or a token/secret validation mechanism to ensure requests originate from legitimate Helloprint systems.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 Helloprint plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Helloprint' in the list, or check the /wp-content/plugins/ directory for a helloprint folder.
    Affected if The plugin is installed and active in the WordPress environment.
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on 'View Details' for the Helloprint plugin to see its version number.
    Affected if The installed version is 2.1.2 or any earlier version (up to and including 2.1.2).
  3. Check if WooCommerce is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that WooCommerce is installed and active.
    Affected if WooCommerce is active, as the vulnerability targets WooCommerce order status modifications.
  4. Test the vulnerable REST endpoint accessibility
    Send a GET or POST request to /wp-json/helloprint/v1/complete_order_from_helloprint_callback without providing any authentication credentials (no API key, nonce, or session).
    Affected if The endpoint responds with HTTP 200 or any status other than 401 (Unauthorized) or 403 (Forbidden), indicating no authorization check is enforced.

The environment is affected if the Helloprint plugin (version 2.1.2 or earlier) is installed alongside active WooCommerce, and the helloprint REST API endpoint is 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add proper authorization and authentication checks to the REST API endpoint, such as a permission_callback verifying user capabilities or a token/secret validation mechanism to ensure requests originate from legitimate Helloprint systems.

Recommended fix Moderate confidence

Helloprint version 2.1.3 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the Helloprint plugin
  4. If update to version 2.1.3 or later is available, click Update Now
  5. If no update is available, deactivate the plugin until an updated version is released

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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