dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-25437

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-25
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 سید محمدامین هاشمی GZSEO gzseo allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects GZSEO: from n/a through <= 2.0.14.

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 GZSEO plugin versions through 2.0.14 allows attackers to exploit incorrectly configured access control security levels, likely enabling unauthorized access to certain functionality or data that should require authentication or higher privileges.

MitigationUpdate GZSEO to the latest patched version when available; alternatively, implement additional access control checks at the application or server level and audit all endpoints for proper authorization enforcement.

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. Identify GZSEO plugin version
    Locate the GZSEO plugin in your CMS/plugin directory and read the version metadata from the main plugin file or version manifest
    Affected if The installed version is 2.0.14 or any earlier version of GZSEO (versions through 2.0.14)
  2. Review access control configuration
    Inspect the plugin settings for any security level, permission, or access control configuration options and verify which user roles are permitted to access plugin functions
    Affected if The plugin exposes functionality to unauthenticated or lower-privileged users due to missing authorization checks
  3. Test sensitive endpoints
    Attempt to access plugin admin pages, AJAX endpoints, or API functions without authentication or while logged in as a low-privilege user
    Affected if Access is granted without proper authorization validation
  4. Audit role-based access settings
    Check the CMS user role configuration and compare which roles can access GZSEO plugin features versus what those roles should legitimately have access to
    Affected if Users with insufficient privileges can access plugin administrative or sensitive functions

You are affected if GZSEO plugin version is 2.0.14 or earlier and the plugin exposes any functionality to users who should not have access based on your access control requirements.

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

Update GZSEO to the latest patched version when available; alternatively, implement additional access control checks at the application or server level and audit all endpoints for proper authorization enforcement.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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