LiveActive security incident?Get immediate response
CVE Record

CVE-2022-36791: WordPress Torro Forms plugin <= 1.0.16 - Authenticated Stored Cross-Site Scripting (XSS) vulnerability

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

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-36791 affects the WordPress Torro Forms plugin through version 1.0.16. A logged-in user with contributor-level access or higher could store malicious script content that runs when another user views it. The issue is medium severity because it requires an authenticated low-privilege user and victim interaction, but it can still affect site trust and admin sessions.

Executive priority

Handle in normal vulnerability management cadence unless affected sites allow many contributors or untrusted content authors. Prioritize public-facing WordPress sites and administrator-heavy workflows because stored XSS can undermine user trust and session safety.

Technical view

The vulnerability is authenticated stored cross-site scripting in Awesome UG Torro Forms for WordPress <= 1.0.16. It is classified as CWE-79 with CVSS 3.1 score 5.4. The vector shows network access, low complexity, low privileges required, user interaction required, changed scope, low confidentiality impact, low integrity impact, and no availability impact.

Likely exposure

Exposure is likely limited to WordPress sites running Torro Forms version 1.0.16 or earlier, especially where contributor-level users can create or edit affected form-related content.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires an authenticated contributor-level or higher account and a separate user viewing the stored content.

Researcher notes

Source evidence identifies the product, version range, vulnerability class, privilege requirement, and CVSS vector. The bundle does not provide exploit details, active exploitation evidence, or a named fixed version, so validation should focus on asset inventory and vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the Torro Forms plugin and its installed version.
  • Treat Torro Forms <= 1.0.16 as vulnerable until vendor guidance says otherwise.
  • Check Patchstack and WordPress plugin guidance for available remediation or replacement direction.
  • Restrict contributor-level access to trusted users while remediation is pending.
  • Disable the plugin on sites where it is not business-critical.

Validation and detection

  • Confirm whether Torro Forms is installed on each WordPress site.
  • Record the exact plugin version and flag versions <= 1.0.16.
  • Review who has contributor-level or higher access on affected sites.
  • Inspect Torro Forms-related content for unexpected script-like markup.
  • After remediation, verify the vulnerable plugin version is no longer present.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-36791 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-36791Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Awesome UGTorro Forms (WordPress plugin)<= 1.0.16Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.