dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1674

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
The Gutena Forms – Contact Form, Survey Form, Feedback Form, Booking Form, and Custom Form Builder plugin for WordPress is vulnerable to unauthorized modification of data due to missing authorization within the save_gutena_forms_schema() function in all versions up to, and including, 1.6.0. This makes it possible for authenticated attackers, with Contributor-level access and above, to update option values to a structured array value on the WordPress site. This can be leveraged to update an option that would create an error on the site and deny service to legitimate users or be used to set some values, that would, for example enable site user registration when it is explicitly disabled.

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 Gutena Forms WordPress plugin lacks proper capability checks in the save_gutena_forms_schema() function, allowing any authenticated user with Contributor-level access or higher to modify WordPress options directly via a structured array. This broken access control enables attackers to toggle settings like user registration or corrupt options to cause denial of service.

MitigationUpdate to version 1.6.1 or later which includes proper authorization checks. Until then, restrict Contributor-level users or disable the plugin if not essential.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Gutena Forms plugin is installed
    Navigate to Plugins > Installed Plugins in WordPress admin, or check the /wp-content/plugins/ directory for the gutena-forms folder
    Affected if The plugin folder exists in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for Gutena Forms version number, or read the version in the plugin's main PHP file header
    Affected if Version is lower than 1.6.1 (the vulnerability exists in versions before the fix)
  3. Confirm plugin is active
    Check the Plugins > Installed Plugins page to see if Gutena Forms is activated
    Affected if Plugin is active and running
  4. Identify users with Contributor role or higher
    Go to Users > All Users in WordPress admin and review the Role column for any users with Contributor, Author, Editor, or Administrator roles
    Affected if At least one user with Contributor-level access or higher exists on the site
  5. Review recent option changes in wp_options
    Query the wp_options table for recent modifications to key settings like users_can_register, default_role, or other site options. Check WordPress activity logs if available.
    Affected if Unwanted or unexpected changes to site options are found that were not made by administrators

A site is affected if Gutena Forms plugin version below 1.6.1 is installed and active, with at least one user having Contributor-level access or higher.

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 to version 1.6.1 or later which includes proper authorization checks. Until then, restrict Contributor-level users or disable the plugin if not essential.

Recommended fix Moderate confidence

1.6.1 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Gutena Forms' plugin in the list
  4. 4. Check if an update is available. If so, update to the latest version (1.6.1 or later)
  5. 5. Alternatively, navigate to Dashboard > Updates and check for plugin updates
  6. 6. After updating, verify the plugin is functioning correctly by testing form creation

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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