LinkedIn credential disclosure via hard-coded OAuth keys
Published Mar 14, 2025 · Updated Apr 8, 2026
Sensitive information exposure in Uxper Civi 2.1.4 and earlier allows remote attackers to read LinkedIn client and secret keys. The theme's includes/class-init.php file embeds the LinkedIn OAuth client identifier and secret as hard-coded values exposed without authentication. No account or user interaction is required, and the documented consequence is disclosure of the embedded LinkedIn integration credentials.
Summary
What happened
Sensitive information exposure in Uxper Civi 2.1.4 and earlier allows remote attackers to read LinkedIn client and secret keys. The theme's includes/class-init.php file embeds the LinkedIn OAuth client identifier and secret as hard-coded values exposed without authentication. No account or user interaction is required, and the documented consequence is disclosure of the embedded LinkedIn integration credentials.
The record
- CVE
- CVE-2024-13773
- Published
- Mar 14, 2025
- Updated
- Apr 8, 2026
- Vendor
- Uxper
- Product
- Civi
- Classifications
- CWE-321, CWE-798, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 14, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 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=0 <=2.1.4
What conditions does exploitation require?
What is affected?
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