Callrail Phone Call TrackingWordPress extension · Callrail
CVE-2022-36796
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability leading to Stored Cross-Site Scripting (XSS) in CallRail, Inc. CallRail Phone Call Tracking plugin <= 0.4.9 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 · moderate confidenceA CSRF vulnerability in the CallRail Phone Call Tracking WordPress plugin (versions <= 0.4.9) allows attackers to trick authenticated administrators into submitting malicious requests that store XSS payloads in the plugin's settings or data fields. When other users view the affected areas, the stored JavaScript executes in their browsers.
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
Callrail Phone Call TrackingWordPress extension
<= 0.4.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if CallRail Phone Call Tracking plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Callrail Callrail Phone Call Tracking' or check the plugins directory for the callrail filesAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find the CallRail plugin, and note the version number displayed below the plugin nameAffected if The version is 0.4.9 or lower (any version <= 0.4.9)
-
Inspect plugin settings for suspicious contentAccess the plugin settings page (typically under Settings > CallRail or a dedicated CallRail menu item) and examine all input fields, text areas, and configuration options for any unexpected JavaScript tags, event handlers, or encoded payloadsAffected if Any settings fields contain raw HTML, script tags, or javascript: URIs that were not intentionally entered by an administrator
-
Check WordPress database for stored XSS in plugin optionsQuery the wp_options table (or options table with appropriate prefix) for option_name values containing 'callrail' or 'call_track', then examine option_value fields for script tags, event handlers (onclick, onerror, etc.), or other XSS vectorsAffected if Any option_value related to the plugin contains unsanitized HTML or JavaScript code
A user is affected if the CallRail Phone Call Tracking plugin version 0.4.9 or lower is installed AND suspicious XSS payloads are found in plugin settings or database options.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the CallRail Phone Call Tracking plugin to the latest version, which should include proper CSRF token validation on all form submissions and AJAX endpoints, along with appropriate input sanitization and output escaping.
Fix this in Callrail Phone Call Tracking
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36796 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36796 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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