dbcve.org
Gozen FormsWordPress extension · Optinlyhq

CVE-2025-6782

HIGH · 7.5 CVSS v3.1 Published 2025-07-04
Fix available
A fix is available. Upgrade to after 1.1.5 or later.
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
The GoZen Forms plugin for WordPress is vulnerable to SQL Injection via the 'forms-id' parameter of the dirGZActiveForm() function in all versions up to, and including, 1.1.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 GoZen Forms WordPress plugin (versions up to 1.1.5) contains a SQL injection vulnerability in the dirGZActiveForm() function. The 'forms-id' parameter is not properly escaped before being used in a SQL query, and the query lacks prepared statement usage, allowing unauthenticated attackers to inject arbitrary SQL commands to extract sensitive database information.

MitigationUpdate the GoZen Forms plugin to version 1.1.6 or later, which should include proper input validation and use of $wpdb->prepare() for all SQL queries incorporating user-supplied parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gozen FormsWordPress extension
Affected:<= 1.1.5

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
None
Availability
None

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

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 GoZen Forms plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'GoZen Forms' or 'Optinlyhq Gozen Forms' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'gozen-forms' or similar.
    Affected if The plugin is not found in the installed plugins list.
  2. Check the installed plugin version
    In the WordPress plugins list, click on the plugin name or view the plugin files to locate the version number in the main PHP file header (usually comments with 'Version: x.x.x').
    Affected if The version is 1.1.5 or lower.
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify that GoZen Forms shows as 'Active' under the plugin status.
    Affected if The plugin is active on the site.
  4. Inspect the vulnerable function code
    Access the plugin files via FTP or file manager, locate the file containing dirGZActiveForm() function (typically in the main plugin PHP file), and examine whether the 'forms-id' parameter is used directly in SQL queries without $wpdb->prepare() or proper escaping (such as esc_sql()).
    Affected if The code shows direct use of $_POST['forms-id'] or similar in SQL without prepared statements.

A site is affected if GoZen Forms plugin version 1.1.5 or lower is installed and active, with the vulnerable dirGZActiveForm() function accessible without proper input sanitization.

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
Upgrade available Upgrade to a release after 1.1.5
Interim mitigation

Update the GoZen Forms plugin to version 1.1.6 or later, which should include proper input validation and use of $wpdb->prepare() for all SQL queries incorporating user-supplied parameters.

Recommended fix Moderate confidence

Latest version of GoZen Forms (beyond 1.1.5)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find GoZen Forms in the plugin list
  4. Check if an update is available and update to the latest version
  5. If no update is available through WordPress, download the latest version from wordpress.org/plugins/gozen-forms/ and reinstall manually
  6. After updating, verify the plugin is functioning correctly

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

Fix this in Gozen Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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