CVE-2021-47982: WordPress Plugin WP-Paginate 2.1.3 Stored XSS via preset
WordPress Plugin WP-Paginate 2.1.3 contains a stored cross-site scripting vulnerability that allows authenticated attackers to inject malicious scripts by manipulating the preset parameter. Attackers can submit POST requests to the plugin settings page with script payloads in the preset parameter that are stored and executed when administrators view the settings.
Security readout for executives and security teams
Plain-English summary
A flaw in the WP-Paginate WordPress plugin version 2.1.3 lets a logged-in user save malicious code into the plugin's settings. When an administrator later opens that settings page, the code runs in their browser, which can lead to account takeover or unwanted changes to the site.
Executive priority
Moderate priority. This is a plugin-specific browser-side flaw that requires an authenticated account and administrator interaction, but successful abuse can hijack an admin session. Address during the next patching cycle; escalate if the site allows self-registration or hosts many low-trust users.
Technical view
CVE-2021-47982 is a stored cross-site scripting (CWE-79) issue in WP-Paginate 2.1.3 by MaxFoundry. An authenticated user can POST a script payload to the plugin's settings page via the preset parameter. The input is stored without adequate sanitization and executed in the administrator's session when settings are viewed. CVSS 3.1 base score is 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N).
Likely exposure
Applies to WordPress sites running WP-Paginate 2.1.3 where non-admin authenticated accounts can reach the plugin settings endpoint. Sites that restrict wp-admin to trusted users have lower exposure; multi-author or public-registration sites face higher risk of an insider or compromised low-privilege account triggering the payload.
Exploitation context
Not listed in CISA KEV. A public proof-of-concept exists on Exploit-DB (49355) and a VulnCheck advisory documents the issue. No cited source confirms active in-the-wild exploitation. Attack requires authenticated access and administrator interaction (viewing settings), which limits opportunistic mass exploitation.
Researcher notes
Stored XSS via the preset parameter with scope change (S:C) reflects that the payload executes in the admin's browser context. PR:L confirms authentication is required, and UI:N indicates the admin does not need to click anything beyond visiting settings. No cited patch commit or fixed version is present in the source bundle; verify current plugin status with the vendor before recommending a specific upgrade version.
Mitigation direction
Check the WP-Paginate plugin page for a version newer than 2.1.3 and update if available.
If no fix is published, deactivate WP-Paginate or restrict access to plugin settings endpoints.
Enforce least privilege on WordPress accounts and disable open user registration where possible.
Deploy a WAF rule to filter script payloads on plugin settings POST requests.
Audit stored plugin options for suspicious HTML or JavaScript content.
Validation and detection
Inventory WordPress sites and confirm which run WP-Paginate 2.1.3 via the Plugins screen or wp-cli.
Review the plugin's stored options (wp_options) for unexpected script or HTML markup in preset values.
Check WordPress access logs for unusual POST requests to WP-Paginate settings endpoints.
In a lab, verify sanitization behavior by submitting benign HTML in the preset field as a low-privileged user.
Confirm administrator sessions use browser XSS protections and unique credentials.
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.
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.
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.
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.