dbcve.org
Torro FormsWordPress extension · Awesome

CVE-2022-36791

MEDIUM · 5.4 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to after 1.0.16 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Authenticated (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Awesome UG Torro Forms plugin <= 1.0.16 at WordPress.

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

Authenticated users with contributor or higher privileges can inject malicious JavaScript through form fields in the Torro Forms WordPress plugin (versions 1.0.16 and earlier). The payload is stored in the database and executes when other users view the affected form content.

MitigationUpdate Torro Forms plugin to version 1.0.17 or later to patch the XSS vulnerability; alternatively, disable or remove the plugin if no update is available.

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
Torro FormsWordPress extension
Affected:<= 1.0.16

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Torro Forms plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Torro Forms' or 'Awesome Torro Forms' in the list. Alternatively, check the /wp-content/plugins/ directory for a torro-forms folder.
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Torro Forms, and view the version number displayed below the plugin name. Or read the main plugin PHP file header for the 'Version' tag.
    Affected if The version is 1.0.16 or earlier
  3. Check for contributor-level or higher user accounts
    In WordPress admin, go to Users > All Users and review the Role column. Identify any users with Contributor, Author, Editor, or Administrator roles.
    Affected if At least one user account has Contributor privileges or higher and can access form builder features
  4. Inspect database for suspicious form field content
    Access the WordPress database (via phpMyAdmin or command line) and query the wp_postmeta table for meta_key containing 'torro' and meta_value containing script tags, javascript:, or onload/onerror attributes. Also check wp_posts where post_type relates to torro forms.
    Affected if Database entries contain encoded or raw JavaScript payloads in form field values

A user is affected if the Torro Forms plugin version is 1.0.16 or earlier AND at least one user with Contributor role or higher exists in the system AND malicious script payloads are present in the database.

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.0.16
Interim mitigation

Update Torro Forms plugin to version 1.0.17 or later to patch the XSS vulnerability; alternatively, disable or remove the plugin if no update is available.

Recommended fix High confidence

Update Torro Forms to version 1.0.17 or later (latest available version)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Torro Forms in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. Verify the updated version number after upgrade

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

Fix this in Torro Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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