dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-28965

HIGH · 8.6 CVSS v3.1 Published 2025-07-16
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
Missing Authorization vulnerability in Md Yeasin Ul Haider URL Shortener exact-links allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects URL Shortener: from n/a through <= 3.0.7.

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

A missing authorization vulnerability in the 'exact-links' URL Shortener by Md Yeasin Ul Haider allows unauthorized users to access functionality that is not properly constrained by Access Control Lists (ACLs). This high-severity (CVSS 8.6) flaw enables attackers to potentially bypass access controls and reach restricted application functions without proper authentication or authorization validation.

MitigationImplement function-level and role-based access control (RBAC) checks on all sensitive endpoints and administrative functions within the URL shortener. Enforce authorization validation before executing any privileged operations and consider upgrading to a patched version once available.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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 exact-links URL Shortener installation
    Search for files or directories containing 'exact-links' in the web root, or check application fingerprints (login pages, headers, or source files referencing 'exact-links' or the author Md Yeasin Ul Haider)
    Affected if The application is the exact-links URL Shortener by Md Yeasin Ul Haider
  2. Check installed version
    Locate version information in the application (typically in a configuration file, README, or about/admin page) and compare against any known version ranges for this CVE
    Affected if The installed version falls within the affected range for this authorization bypass vulnerability
  3. Enumerate application endpoints
    Review available routes, pages, or API endpoints in the application, particularly admin, user management, URL creation/deletion, or statistics functions
    Affected if The application exposes administrative or privileged functionality through web-accessible endpoints
  4. Test unauthorized access to sensitive functions
    Attempt to access identified sensitive endpoints (admin panels, user data, URL management) directly via HTTP requests without providing valid authentication credentials or session cookies
    Affected if Requests to restricted endpoints succeed without proper authorization validation, returning actual functionality rather than an access denied error

A user is affected if they have the exact-links URL Shortener installed with unauthenticated or unauthorized access possible to restricted application functions.

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

Implement function-level and role-based access control (RBAC) checks on all sensitive endpoints and administrative functions within the URL shortener. Enforce authorization validation before executing any privileged operations and consider upgrading to a patched version once available.

Recommended fix Moderate confidence

3.0.8 or latest version (version higher than 3.0.7)

  1. Check the WordPress plugin repository or contact the vendor for the latest version of the URL Shortener plugin by Md Yeasin Ul Haider
  2. Upgrade the plugin to the latest available version that includes the security fix
  3. Verify the upgrade completes successfully
  4. Test the URL shortener functionality to ensure it works correctly after the update
  5. Review user roles and permissions to ensure proper access controls are in place

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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