dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-58639

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 Ali Khallad Contact Form By Mega Forms mega-forms allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Contact Form By Mega Forms: from n/a through <= 1.6.1.

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 exists in the Contact Form By Mega Forms WordPress plugin (versions <= 1.6.1) that allows exploiting incorrectly configured access control security levels, potentially enabling unauthenticated or improperly authorized users to access functionality they should not have permission to use.

MitigationImplement proper authorization checks on all sensitive functions and enforce the principle of least privilege; update to the latest patched version of the plugin when 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Mega Forms plugin is installed
    Navigate to WordPress admin dashboard > Plugins and locate 'Contact Form By Mega Forms' in the installed plugins list, or check the file system at wp-content/plugins/ for a mega-forms directory
    Affected if Plugin is not found or not installed (not vulnerable if absent)
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on the Mega Forms plugin to view version details, or inspect the main plugin PHP file header for the 'Version:' value, or check the readme.txt file in the plugin directory
    Affected if Version is 1.6.1 or lower (versions above 1.6.1 are not affected)
  3. Examine access control security level configuration
    Navigate to Mega Forms plugin settings in WordPress admin panel, locate any access control, user permissions, or security level configuration sections. Identify which user roles are assigned to sensitive functions such as form creation, editing, deletion, or settings modification
    Affected if Access control security levels are incorrectly configured, allowing users with insufficient privileges to access functionality they should not have permission to use

A user is affected if the Mega Forms plugin version is 1.6.1 or lower AND the plugin access control security levels are misconfigured to grant improper permissions to low-privileged users.

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

Implement proper authorization checks on all sensitive functions and enforce the principle of least privilege; update to the latest patched version of the plugin when available.

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-58639 — 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-58639 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