dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67913

MEDIUM · 6.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 →
74/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 Aruba.it Dev Aruba HiSpeed Cache aruba-hispeed-cache allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Aruba HiSpeed Cache: from n/a through < 3.0.3.

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 Aruba HiSpeed Cache plugin allows attackers to access functionality that is not properly constrained by Access Control Lists (ACLs). This broken access control issue affects versions prior to 3.0.3, potentially enabling unauthenticated or unauthorized users to reach protected functionality within the plugin.

MitigationUpgrade to Aruba HiSpeed Cache version 3.0.3 or later which contains the authorization fix. If immediate upgrade is not possible, review and enforce proper ACL constraints on all sensitive plugin endpoints and functions.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Locate the Aruba HiSpeed Cache plugin installation
    Check your web server's plugin directory for the Aruba HiSpeed Cache plugin files. Common paths include /wp-content/plugins/aruba-hispeed-cache/ or similar. Verify the plugin directory exists.
    Affected if The plugin directory exists on the system.
  2. Identify the installed version
    Open the main plugin file (typically hispeed-cache.php or similar) and locate the version definition comment or the Version header in the plugin metadata. Alternatively, check the plugin's readme.txt file for the Stable tag entry.
    Affected if A version number lower than 3.0.3 is found in the plugin files.
  3. Compare version against affected range
    If a version number was found, compare it numerically to 3.0.3. Versions such as 3.0.2, 3.0.1, 3.0.0, 2.x.x, 1.x.x or any version prior to 3.0.3 are considered affected.
    Affected if The installed version is earlier than 3.0.3.
  4. Inspect plugin access control configuration
    Examine the plugin's PHP files for access control checks (functions like current_user_can, check_admin_referer, is_user_logged_in) around sensitive functions or AJAX endpoints. Look for any publicly accessible endpoints that should require authentication.
    Affected if Sensitive plugin functions or endpoints lack proper authorization checks.

You are affected if the Aruba HiSpeed Cache plugin is installed with a version lower than 3.0.3 and contains plugin endpoints or functions that are accessible without proper authorization validation.

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

Upgrade to Aruba HiSpeed Cache version 3.0.3 or later which contains the authorization fix. If immediate upgrade is not possible, review and enforce proper ACL constraints on all sensitive plugin endpoints and functions.

Recommended fix High confidence

Upgrade to Aruba HiSpeed Cache version 3.0.3 or later

  1. Identify the current version of Aruba HiSpeed Cache plugin installed on the WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate Aruba HiSpeed Cache in the plugins list
  4. If an update to version 3.0.3 or later is available, click Update Now to apply the security patch
  5. Verify the update completed successfully by checking the plugin version after update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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