Skip to main content
Vulnerability Database/CVE-2025-32483

CVE-2025-32483: Request Call Back Stored XSS Vulnerability

CVE-2025-32483 is a stored cross-site scripting vulnerability in the Request Call Back WordPress plugin that enables attackers to inject malicious scripts. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-32483 Overview

CVE-2025-32483 is a stored Cross-Site Scripting (XSS) vulnerability in the Scott Salisbury Request Call Back WordPress plugin. The flaw affects all plugin versions up to and including 1.4.1. The vulnerability stems from improper neutralization of user-supplied input during web page generation [CWE-79]. Authenticated attackers with high privileges can inject malicious scripts that persist across sessions and execute in the browsers of users who view the affected pages.

Critical Impact

Stored XSS enables script execution in victim browsers, which attackers can leverage for session theft, credential harvesting, and administrative action abuse within the WordPress site.

Affected Products

  • Scott Salisbury Request Call Back WordPress plugin
  • All versions from n/a through 1.4.1
  • WordPress sites with the vulnerable plugin installed and active

Discovery Timeline

  • 2025-04-09 - CVE-2025-32483 published to the National Vulnerability Database
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-32483

Vulnerability Analysis

The vulnerability is a stored Cross-Site Scripting (XSS) issue classified under [CWE-79]. The plugin fails to properly sanitize or encode user-supplied input before storing it and later rendering it in web pages. Because the payload persists in the backend, any user who loads the affected page triggers execution of the attacker-controlled JavaScript.

Exploitation requires an authenticated session with elevated privileges and user interaction from a victim. The scope is changed, meaning the injected script can affect resources beyond the vulnerable component, such as other authenticated users browsing the WordPress admin interface.

Root Cause

The root cause is missing or insufficient output encoding and input sanitization within the Request Call Back plugin. User-controlled data flows into HTML output contexts without applying WordPress sanitization helpers such as esc_html(), esc_attr(), or wp_kses(). This allows raw HTML and JavaScript to be rendered by the browser.

Attack Vector

An attacker with high-privilege access submits a payload containing JavaScript through an input field exposed by the plugin. The plugin stores the payload without sanitization. When a legitimate user visits a page that renders the stored value, the browser executes the attacker's script in the victim's authenticated context. Payloads can hijack sessions, perform actions as the victim, or redirect users to attacker-controlled infrastructure.

Technical details are documented in the Patchstack WordPress Vulnerability Report.

Detection Methods for CVE-2025-32483

Indicators of Compromise

  • Unexpected <script> tags, event handlers, or javascript: URIs stored in Request Call Back plugin database tables or options
  • Outbound requests from administrator browsers to unfamiliar domains after visiting plugin-rendered pages
  • WordPress audit log entries showing content modifications by non-standard high-privilege accounts

Detection Strategies

  • Scan the WordPress database for HTML or JavaScript artifacts within fields managed by the request-call-back plugin
  • Review web server access logs for POST requests to plugin endpoints containing encoded script payloads
  • Deploy a web application firewall (WAF) rule that flags XSS signatures targeting plugin administration pages

Monitoring Recommendations

  • Monitor administrator and editor account activity for anomalous content submissions to plugin-managed forms
  • Enable Content Security Policy (CSP) reporting to capture blocked inline script executions
  • Track plugin version inventory across managed WordPress sites and alert on installations at or below version 1.4.1

How to Mitigate CVE-2025-32483

Immediate Actions Required

  • Update the Request Call Back plugin to a version later than 1.4.1 as soon as a vendor-released patch is available
  • Audit high-privilege WordPress accounts and rotate credentials for any that may have been misused
  • Review all plugin-managed content and purge any stored payloads containing executable HTML or JavaScript

Patch Information

At the time of publication, the Patchstack advisory lists all versions through 1.4.1 as vulnerable. Administrators should consult the Patchstack WordPress Vulnerability Report for the latest patched release information. If no fixed version is available, deactivate and remove the plugin until a patch is published.

Workarounds

  • Deactivate the Request Call Back plugin on affected WordPress sites until a patched release is confirmed
  • Restrict high-privilege WordPress roles to a minimal, trusted set of administrators
  • Deploy a WAF ruleset that blocks XSS payloads targeting /wp-admin/ endpoints associated with the plugin
  • Enforce a strict Content Security Policy that disallows inline scripts and unknown external script sources

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.