CVE-2026-4063
Unauthorized Data Modification in WPZOOM Social Icons Plugin
Publication date: 2026-03-13
Last updated on: 2026-03-13
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wpzoom | social_icons_widget_and_block | to 4.5.8 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Social Icons Widget & Block by WPZOOM plugin for WordPress has a vulnerability due to a missing capability check in the add_menu_item() method. This method is hooked to the admin_menu and performs actions like wp_insert_post() and update_post_meta() to create a sharing configuration without verifying if the current user has administrator-level permissions.
As a result, authenticated users with Subscriber-level access or higher can trigger the creation of a published wpzoom-sharing configuration post with default social sharing button settings. This causes social sharing buttons to be automatically injected into all post content on the frontend.
How can this vulnerability impact me? :
This vulnerability allows users with low-level access (Subscriber-level and above) to modify data by creating published sharing configuration posts without proper authorization.
The impact is limited to unauthorized data modification, specifically the automatic injection of social sharing buttons into all post content on the frontend.
The CVSS score of 4.3 indicates a low to medium severity impact, with no confidentiality or availability impact, but with integrity impact due to unauthorized changes.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know