CVE-2023-54333
Critical SQL Injection in Social-Share-Buttons 2.2.3 Enables Data Theft
Publication date: 2026-01-13
Last updated on: 2026-01-13
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| supsystic | social-share-buttons | 2.2.3 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2023-54333 is a critical SQL injection vulnerability in the Social-Share-Buttons WordPress plugin version 2.2.3. The flaw exists in the 'project_id' parameter, which is not properly sanitized, allowing attackers to inject malicious SQL commands via crafted POST requests. This enables attackers to manipulate database queries and potentially retrieve or steal the entire contents of the database. [3, 4]
How can this vulnerability impact me? :
This vulnerability can have a severe impact by allowing attackers to perform unauthorized SQL injection attacks that can lead to the theft of the entire database contents. This means sensitive data stored in the database can be exposed, manipulated, or stolen, potentially compromising the security and integrity of your website and its users. [3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted POST requests to the vulnerable 'project_id' parameter and observing the responses. Two common SQL injection detection techniques are Boolean-based blind SQL injection and Time-based blind SQL injection. Example payloads include: 1. Boolean-based blind SQL injection payload: action=social-sharing-share&project_id=378116348' or '3724'='3724' AND 7995=7995 AND 'rQVH'='rQVH&network_id=5&post_id= 2. Time-based blind SQL injection payload: action=social-sharing-share&project_id=378116348' or '3724'='3724' AND (SELECT 9167 FROM (SELECT(SLEEP(5)))dQDw) AND 'KWbC'='KWbC&network_id=5&post_id= You can use tools like curl or Burp Suite to send these POST requests and monitor the response times or content to confirm the presence of the vulnerability. [4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Social-Share-Buttons plugin to a version that patches this SQL injection vulnerability if available. If an update is not available, restrict access to the vulnerable endpoints, implement web application firewall (WAF) rules to block malicious SQL payloads targeting the 'project_id' parameter, and monitor for suspicious POST requests. Additionally, consider disabling or removing the plugin until a fix is applied to prevent exploitation. [4]