dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-30797

HIGH · 7.5 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 bigdrop.gr Greek Multi Tool – Fix peralinks, accents, auto create menus and more greek-multi-tool allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Greek Multi Tool – Fix peralinks, accents, auto create menus and more: from n/a through <= 2.3.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

This is a Missing Authorization vulnerability in the Greek Multi Tool WordPress plugin (versions <= 2.3.1). The plugin has incorrectly configured access control security levels, allowing attackers to bypass proper authorization checks and access functionality they should not have permission to use. The CVSS 7.5 score indicates unauthenticated attackers can potentially exploit this to perform privileged actions.

MitigationUpdate the Greek Multi Tool plugin to the latest version which should include proper authorization checks. Until then, restrict access to affected plugin endpoints and review user capability requirements for all plugin 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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 Greek Multi Tool plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'greek-multi-tool' or similar Greek-themed plugin folder. Use file system commands or FTP to enumerate installed plugins.
    Affected if The plugin folder exists in the WordPress plugins directory.
  2. Identify the installed version number
    Open the main PHP file of the Greek Multi Tool plugin (usually the primary PHP file in the plugin folder) and locate the version declaration, typically found in the plugin header comment as 'Version: x.x.x' or in a constant like 'define("PLUGIN_VERSION", "...")'.
    Affected if The version extracted from the plugin header or code is 2.3.1 or lower.
  3. Verify plugin activation status
    Check the WordPress database table wp_options for option_name containing 'active_plugins', or log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to confirm if Greek Multi Tool is listed as active.
    Affected if The plugin appears in the list of active WordPress plugins.
  4. Confirm authorization exposure
    Review the plugin PHP files for capability checks using functions like current_user_can(), wp_get_current_user(), or check_admin_referer(). Look for AJAX handlers or form processing endpoints that may lack these checks. Compare the number and placement of authorization checks against typical WordPress security patterns.
    Affected if Plugin files contain fewer or improperly implemented capability checks, or AJAX/public endpoints lack authorization validation.

If the Greek Multi Tool plugin is installed, active, and its version is 2.3.1 or lower, the environment is affected by this missing authorization vulnerability and should be updated to the latest version.

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

Update the Greek Multi Tool plugin to the latest version which should include proper authorization checks. Until then, restrict access to affected plugin endpoints and review user capability requirements for all plugin functions.

Recommended fix Moderate confidence

Version higher than 2.3.1 (likely 2.3.2 or later)

  1. Update the Greek Multi Tool plugin to the latest available version from the WordPress plugin repository or vendor's official source
  2. After updating, verify that proper authorization controls are now enforced on all sensitive functions and API endpoints
  3. Test that users without proper permissions can no longer access administrative features
  4. Review user roles and permissions to ensure they align with the principle of least privilege

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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