dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-10690

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
The Goza - Nonprofit Charity WordPress Theme theme for WordPress is vulnerable to unauthorized arbitrary file uploads due to a missing capability check on the 'beplus_import_pack_install_plugin' function in all versions up to, and including, 3.2.2. This makes it possible for unauthenticated attackers to upload zip files containing webshells disguised as plugins from remote locations to achieve remote code execution.

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 · high confidence

The Goza WordPress theme (versions up to 3.2.2) lacks a capability check on the 'beplus_import_pack_install_plugin' function, enabling unauthenticated attackers to upload malicious ZIP archives containing webshells disguised as plugins, achieving remote code execution.

MitigationUpdate the Goza theme to version 3.2.3 or later which includes proper capability validation. As an interim measure, disable the theme or block access to the vulnerable endpoint at the server level.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify if Goza theme is installed
    In the WordPress admin dashboard, go to Appearance > Themes and look for the Goza theme. Alternatively, check the /wp-content/themes/goza/ directory on the server and locate the style.css file to read the 'Version:' header.
    Affected if Goza theme is present on the WordPress installation
  2. Determine the installed Goza theme version
    Open the theme's style.css file (typically at /wp-content/themes/goza/style.css) and locate the Version field in the file header comment. Compare this version number to the affected range (versions up to 3.2.2).
    Affected if The version is 3.2.2 or lower (any version up to and including 3.2.2)
  3. Locate the vulnerable function in theme files
    Search the theme directory (/wp-content/themes/goza/) for the string 'beplus_import_pack_install_plugin' using grep or a file content search. This function handles plugin installation and lacks the capability check.
    Affected if The function 'beplus_import_pack_install_plugin' exists in the theme files, indicating the vulnerable code is present
  4. Inspect for suspicious uploaded plugins or ZIP files
    Review the /wp-content/plugins/ directory for any recently added plugins or unexpected ZIP archives. Check file creation timestamps for items added around the time of suspected compromise.
    Affected if Unexpected plugin directories or ZIP files are present, especially those not installed through the official WordPress repository
  5. Scan for webshell files in the plugins directory
    Examine PHP files in /wp-content/plugins/ for common webshell indicators such as base64_decode, shell_exec, system, passthru, or eval functions with suspicious encoded content. Use a security scanner or manually review unfamiliar plugin folders.
    Affected if PHP files containing webshell code or suspicious remote execution functions are found in the plugins directory

You are affected if the Goza theme is installed with version 3.2.2 or lower and the vulnerable beplus_import_pack_install_plugin function is present in the theme code.

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 the Goza theme to version 3.2.3 or later which includes proper capability validation. As an interim measure, disable the theme or block access to the vulnerable endpoint at the server level.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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