CVE-2026-0812
Stored XSS in LinkedIn SC WordPress Plugin Allows Admin Script Injection
Publication date: 2026-01-14
Last updated on: 2026-01-14
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | linkedin_sc | 1.1.9 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the LinkedIn SC plugin for WordPress. It occurs because the plugin does not properly sanitize or escape input for the 'linkedin_sc_date_format', 'linkedin_sc_api_key', and 'linkedin_sc_secret_key' parameters. Authenticated users with administrator-level access or higher can inject malicious scripts into pages. These scripts then execute whenever any user accesses the affected page, potentially compromising user data or site integrity.
How can this vulnerability impact me? :
The vulnerability allows attackers with administrator-level access to inject arbitrary web scripts into the WordPress site. This can lead to unauthorized actions such as stealing user credentials, hijacking user sessions, defacing the website, or distributing malware to visitors. Since the malicious scripts execute whenever a user accesses the injected page, it can affect all users visiting the site, potentially leading to data breaches or loss of trust.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the WordPress site is using the LinkedIn SC plugin version 1.1.9 or earlier. Since the vulnerability involves stored Cross-Site Scripting via the 'linkedin_sc_date_format', 'linkedin_sc_api_key', and 'linkedin_sc_secret_key' parameters, detection involves inspecting these plugin settings and any stored values for malicious scripts. On the system, you can check the installed plugin version via WP-CLI with the command: `wp plugin list --status=active` and look for 'linkedin-sc' version 1.1.9 or below. Additionally, you can search the WordPress database options table for suspicious script content in the options named 'linkedin_sc_date_format', 'linkedin_sc_api_key', and 'linkedin_sc_secret_key' using SQL commands like: `SELECT option_name, option_value FROM wp_options WHERE option_name IN ('linkedin_sc_date_format', 'linkedin_sc_api_key', 'linkedin_sc_secret_key') AND option_value LIKE '%<script>%'`. Network detection is limited since the exploit requires authenticated admin access, but monitoring for unusual admin activity or unexpected changes in plugin settings may help. There are no specific network commands provided in the resources. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the LinkedIn SC plugin to a version later than 1.1.9 where the vulnerability is fixed. If an update is not immediately available, restrict administrator-level access to trusted users only, as exploitation requires authenticated admin privileges. Review and sanitize the plugin settings for 'linkedin_sc_date_format', 'linkedin_sc_api_key', and 'linkedin_sc_secret_key' to remove any injected scripts. Additionally, consider disabling or removing the plugin temporarily to prevent exploitation. Implementing strict input validation and output escaping in the plugin settings is recommended, but this requires a plugin update. Monitoring and auditing admin activities related to this plugin can also help mitigate risk until a patch is applied. [1, 3]