dbcve.org
Easy Social IconsWordPress extension · Cybernetikz

CVE-2023-48336

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to after 3.2.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in cybernetikz Easy Social Icons allows Stored XSS.This issue affects Easy Social Icons: from n/a through 3.2.4.

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 confidence

Stored XSS vulnerability in the Easy Social Icons WordPress plugin allows attackers to inject malicious JavaScript through plugin settings (social icon fields) that gets stored in the database and executes when administrators or users view the affected pages in the WordPress dashboard or frontend.

MitigationUpdate Easy Social Icons to the latest patched version. If no update is available, disable the plugin. Alternatively, implement server-side input validation and output escaping on all user-supplied data in custom code or a forked version.

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
Easy Social IconsWordPress extension
Affected:<= 3.2.4

CVSS 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Easy Social Icons plugin is installed
    Check the WordPress plugin directory (wp-content/plugins/easy-social-icons/) or query wp_plugins table for 'easy-social-icons' entry. In WordPress admin, go to Plugins > Installed Plugins and look for 'Easy Social Icons' by Cybernetikz.
    Affected if Plugin files exist in the plugin directory or plugin record found in database.
  2. Check installed plugin version
    Open the main plugin file (easy-social-icons/easy-social-icons.php) and locate the 'Version' header comment, or query the wp_options table for the option containing version info (typically 'easy_social_icons_version' or similar). Compare against affected range: <= 3.2.4.
    Affected if Installed version number is 3.2.4 or lower.
  3. Inspect stored social icon settings in database
    Query the wp_options table for options related to easy social icons (look for options containing 'easy_social' or 'cn_social'). Example SQL: SELECT * FROM wp_options WHERE option_name LIKE '%easy_social%' OR option_name LIKE '%cn_social%'. Examine the option_value for any HTML, script tags, or JavaScript event handlers (onerror, onload, onclick, etc.) embedded in icon URL fields or social platform names.
    Affected if Database contains HTML tags, script elements, or JavaScript event handlers in social icon configuration fields.
  4. Check plugin settings page for unescaped output
    Access the plugin settings page in WordPress admin (usually under Settings > Easy Social Icons). Manually inspect each social icon field (icon URL, profile URL, platform name) for any values that might render as executable JavaScript when the page displays them. Look for fields containing <script>, javascript:, or event handlers.
    Affected if Plugin settings page displays user-supplied content that renders as executable code rather than escaped text.

The environment is affected if the Easy Social Icons plugin version is 3.2.4 or lower AND the plugin is active, as this combination enables the stored XSS attack vector through unsanitized social icon field inputs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 3.2.4
Interim mitigation

Update Easy Social Icons to the latest patched version. If no update is available, disable the plugin. Alternatively, implement server-side input validation and output escaping on all user-supplied data in custom code or a forked version.

Fix this in Easy Social Icons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-48336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-48336 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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