Administrator-level stored XSS via unescaped settings
Published Jan 14, 2026 · Updated Jan 14, 2026
Stored XSS in LinkedIn SC 1.1.9 and earlier allows remote authenticated users with administrator access to inject scripts through plugin settings. The settings handler stores the linkedin_sc_date_format, linkedin_sc_api_key, and linkedin_sc_secret_key values without sanitizing them, and the settings page emits them without output escaping. Administrator-level WordPress access is required; injected scripts execute in a user's browser when the affected page is viewed.
Summary
What happened
Stored XSS in LinkedIn SC 1.1.9 and earlier allows remote authenticated users with administrator access to inject scripts through plugin settings. The settings handler stores the linkedin_sc_date_format, linkedin_sc_api_key, and linkedin_sc_secret_key values without sanitizing them, and the settings page emits them without output escaping. Administrator-level WordPress access is required; injected scripts execute in a user's browser when the affected page is viewed.
The record
- CVE
- CVE-2026-0812
- Published
- Jan 14, 2026
- Updated
- Jan 14, 2026
- Vendor
- Guillaume Viguier-Just
- Product
- LinkedIn SC
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 14, 2026CVE publishedPublication date reported by the CVE source.
- Jan 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=1.1.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo