CVE-2024-12443 MEDIUM

CVE-2024-12443: CRM Perks – WordPress HelpDesk Integration – Zendesk, Freshdesk, HelpScout <= 1.1.6 - Authenticated (Contributor+) Stored Cross-Site Scripting

Vendor Crmperks
Product CRM Perks – WordPress HelpDesk Integration – Zendesk, Freshdesk, HelpScout
Weakness CWE-79 · XSS
Published December 16, 2024
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

The CRM Perks – WordPress HelpDesk Integration – Zendesk, Freshdesk, HelpScout plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'crm-perks-tickets' shortcode in all versions up to, and including, 1.1.6 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Explanation of Vulnerability in Simple Terms

02Summary

The CRM Perks WordPress plugin for HelpDesk integration contains a stored cross-site scripting (XSS) vulnerability in versions up to 1.1.6. An authenticated user with low privileges can inject malicious scripts that execute in the browsers of other site users, potentially compromising accounts or stealing sensitive data. The vulnerability affects the plugin's scope across the site.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers when they view affected pages.

Potential impact on your site

04Site Impact

Other site users, including admins, may have their sessions hijacked or data stolen if they view pages containing the injected script.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress account (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

December 16, 2024 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE