dbcve.org
Crm Perks FormsWordPress extension · Crmperks

CVE-2022-38467

MEDIUM · 6.1 CVSS v3.1 Published 2023-01-14
Fix available
A fix is available. Upgrade to after 1.1.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Reflected Cross-Site Scripting (XSS) vulnerability in CRM Perks Forms – WordPress Form Builder <= 1.1.0 ver.

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 · moderate confidence

Reflected Cross-Site Scripting (XSS) vulnerability in the CRM Perks Forms WordPress plugin version 1.1.0 and below allows attackers to inject malicious JavaScript through unsanitized user input that is reflected in the application's response without proper output encoding.

MitigationUpdate CRM Perks Forms to the latest version; until then, implement output escaping using WordPress sanitization functions (esc_html, esc_attr, esc_url) on all user-supplied data before reflecting it in HTML responses.

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
Crm Perks FormsWordPress extension
Affected:<= 1.1.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'CRM Perks Forms' or 'Crmperks Crm Perks Forms' in the installed plugins list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'crm-perks-forms' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Identify installed version
    In WordPress Admin > Plugins, find the CRM Perks Forms entry and check the version number displayed beneath the plugin name. Alternatively, open the main plugin PHP file (usually in /wp-content/plugins/[plugin-folder]/ and look for a version comment or defined constant.
    Affected if Version is 1.1.0 or lower
  3. Verify plugin is active
    In WordPress Admin > Plugins, confirm the plugin shows as 'Active' rather than 'Inactive' or 'Must Use'. The vulnerability only applies when the plugin is actively processing requests.
    Affected if Plugin status is Active
  4. Identify reflected input points
    Locate the plugin files that handle form submissions and display form data. Look for PHP files that use $_GET, $_POST, or similar superglobals and output the values directly to HTML without using WordPress sanitization functions like esc_html(), esc_attr(), or esc_url().
    Affected if User-supplied data from form submissions or URL parameters is being output to HTML without escaping functions
  5. Test for XSS vulnerability
    Submit a test form or crafted URL with a benign XSS payload (such as <script>alert('XSS')</script> or <img src=x onerror=alert('XSS')>) through the plugin's form inputs or URL parameters. Examine if the payload is reflected unescaped in the response.
    Affected if The payload appears in the browser-rendered page source without HTML entity encoding

A user is affected if the CRM Perks Forms plugin is installed, active, and running version 1.1.0 or lower, with user input being reflected in HTML responses without proper escaping.

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.

From vendor data
Upgrade available Upgrade to a release after 1.1.0
Interim mitigation

Update CRM Perks Forms to the latest version; until then, implement output escaping using WordPress sanitization functions (esc_html, esc_attr, esc_url) on all user-supplied data before reflecting it in HTML responses.

Fix this in Crm Perks Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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