CVE-2022-2763

What it actually does

Stored XSS flaw allowing unsanitized and unescaped Icons settings to persist malicious scripts that execute in browsers of site visitors and other administrators.

Why it matters to the business

High-privilege users can inject persistent scripts that compromise user sessions, steal data, or alter site appearance across multisite or hardened WordPress installations, increasing operational risk and potential regulatory exposure.

How an attack unfolds

An authenticated administrator navigates to the plugin Icons settings, inserts script payloads into unsanitized fields, saves the configuration, and the stored scripts execute for any user who later views affected pages or admin screens.

How to fix it

Upgrade the WP Socializer plugin to version 7.3 or newer; review and sanitize existing Icons settings; restrict admin accounts and enable content security policy headers as defense-in-depth.

How to confirm the fix worked

Confirm plugin version is at least 7.3; attempt to save a test script tag in Icons settings and verify it is escaped or rejected; scan plugin settings tables for residual script tags.

Typical attack path

1. Obtain high-privilege WordPress account (admin)
2. Access WP Socializer Icons configuration page
3. Insert malicious JavaScript into one or more icon fields without sanitization
4. Save settings so payload is stored server-side
5. Wait for victim users or administrators to load pages that render the icons
6. Script executes in victim browser under site origin

How to detect it

Search WordPress options tables or plugin configuration exports for script, img, or svg tags containing event handlers or javascript: URIs; review web server and WordPress debug logs around the time of settings changes for unusual POST requests to the plugin options endpoint.

• wp_socializer_icons
• <script
• onerror=
• javascript:
• data:text/html

What your security team should do

• Immediately update WP Socializer to 7.3+ on all sites
• Audit admin accounts and remove unnecessary high-privilege users
• Enable WordPress multisite hardening and disallow unfiltered_html where possible
• Add CSP headers that restrict script sources
• Monitor for anomalous script tags in plugin option values