dbcve.org
Gozen FormsWordPress extension · Optinlyhq

CVE-2025-6783

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 emdedSc() 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 an unauthenticated SQL injection vulnerability in the embedSc() function. The 'forms-id' parameter is not properly sanitized before being used in a database query, allowing attackers to inject arbitrary SQL commands.

MitigationUpdate the GoZen Forms plugin to version 1.1.6 or later which contains the patched code with proper parameter sanitization and prepared SQL statements.

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
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'GoZen Forms' or 'Optinlyhq Gozen Forms' in the list of active plugins.
    Affected if The plugin is not installed on the WordPress site.
  2. Check installed plugin version
    In the Plugins list, click on the plugin name or view details to find the installed version number. Compare this against the affected range: <= 1.1.5.
    Affected if Installed version is 1.1.5 or lower.
  3. Identify if embed functionality is in use
    Review site content, pages, posts, or widgets for embedded forms using the plugin's shortcode (typically [gozenforms id=] or similar embed patterns). Check if the 'forms-id' parameter is being passed in URLs or form embeddings.
    Affected if The embedSc() function with 'forms-id' parameter is actively used on the site.
  4. Inspect HTTP requests for vulnerable parameter
    If forms are embedded, examine the network requests when loading the embedded form page. Look for requests containing the 'forms-id' parameter being passed without proper sanitization.
    Affected if The 'forms-id' parameter accepts and processes raw input without sanitization.

A site is affected if GoZen Forms plugin version 1.1.5 or lower is installed AND the embed functionality with the 'forms-id' parameter is being used, allowing unauthenticated SQL injection via that parameter.

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 contains the patched code with proper parameter sanitization and prepared SQL statements.

Recommended fix Moderate confidence

GoZen Forms 1.1.6 or latest available version

  1. 1. Log in to WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate GoZen Forms in the plugin list
  4. 4. If an update is available, click 'Update Now' to update GoZen Forms to the latest version
  5. 5. After updating, verify the plugin is functioning correctly by testing form rendering

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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