CRITICALCVE-2025-31911CVSS 9.3

CVE-2025-31911: SQL Injection in Social Share And Social Locker

Platform

wordpress

Component

social-share-and-social-locker-arsocial

Fixed in

1.4.3

AI Confidence: highNVDEPSS 0.2%Reviewed: May 2026

CVE-2025-31911 describes a critical SQL Injection vulnerability discovered in the Social Share And Social Locker WordPress plugin. This flaw allows attackers to perform blind SQL injection, potentially leading to unauthorized data access and manipulation. The vulnerability affects versions from 0 up to and including 1.4.2, and a patch is available in version 1.4.3.

WordPress

Detect this CVE in your project

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

Impact and Attack Scenarios

The SQL Injection vulnerability in Social Share And Social Locker allows attackers to bypass security measures and directly interact with the underlying database. Due to the 'blind' nature of the injection, attackers must infer data through multiple queries, making exploitation potentially time-consuming but still highly impactful. Successful exploitation could lead to the extraction of sensitive user data, including usernames, passwords, email addresses, and potentially even financial information if the plugin handles such data. Furthermore, an attacker could modify database records, leading to data corruption or denial of service. This vulnerability shares characteristics with other SQL injection flaws, where attackers leverage malformed SQL queries to gain unauthorized access.

Exploitation Context

CVE-2025-31911 was publicly disclosed on 2025-04-03. The vulnerability's severity is high due to the potential for data exfiltration and modification. Currently, there are no known public exploits or active campaigns targeting this specific vulnerability, but the blind SQL injection nature means exploitation is possible. It is not listed on the CISA KEV catalog as of this writing.

Threat Intelligence

Exploit Status

Proof of ConceptUnknown
CISA KEVNO
Internet ExposureHigh

EPSS

0.23% (46% percentile)

CISA SSVC

Exploitationnone
Automatableyes
Technical Impacttotal

CVSS Vector

THREAT INTELLIGENCE· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L9.3CRITICALAttack VectorNetworkHow the attacker reaches the targetAttack ComplexityLowConditions required to exploitPrivileges RequiredNoneAuthentication level needed to attackUser InteractionNoneWhether a victim must take actionScopeChangedImpact beyond the vulnerable componentConfidentialityHighRisk of sensitive data exposureIntegrityNoneRisk of unauthorized data modificationAvailabilityLowRisk of service disruptionnextguardhq.com · CVSS v3.1 Base Score
What do these metrics mean?
Attack Vector
Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
Attack Complexity
Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
Privileges Required
None — unauthenticated. No login or credentials needed to exploit.
User Interaction
None — attack is automatic and silent. Victim does nothing: no click, no file open.
Scope
Changed — successful attack can pivot beyond the vulnerable component to other systems or the host OS.
Confidentiality
High — complete confidentiality loss. Attacker can read all data: credentials, keys, personal data.
Integrity
None — no integrity impact. Attacker cannot modify data.
Availability
Low — partial or intermittent denial of service. Attacker can degrade performance.

Affected Software

Componentsocial-share-and-social-locker-arsocial
Vendorreputeinfosystems
Affected rangeFixed in
0 – 1.4.21.4.3

Weakness Classification (CWE)

Timeline

  1. Reserved
  2. Published
  3. Modified
  4. EPSS updated

Mitigation and Workarounds

The primary mitigation for CVE-2025-31911 is to immediately upgrade the Social Share And Social Locker plugin to version 1.4.3 or later. If upgrading is not immediately feasible due to compatibility issues or breaking changes, consider temporarily disabling the plugin to prevent exploitation. While a direct WAF rule is difficult to implement for blind SQL injection, implementing a WAF rule that blocks suspicious SQL query patterns targeting the plugin's endpoints could offer some protection. Monitor WordPress access logs for unusual SQL query patterns originating from the plugin’s endpoints. After upgrading, confirm the vulnerability is resolved by attempting a test SQL injection query through the plugin’s functionality and verifying that it is properly sanitized.

How to fix

Update the Social Share And Social Locker plugin to the latest available version to mitigate the blind SQL injection vulnerability. Check for updates in the WordPress repository or contact the developer for more information about the patched version. Implement additional security measures, such as user input validation and sanitization, to prevent future vulnerabilities.

CVE Security Newsletter

Vulnerability analysis and critical alerts directly to your inbox.

Frequently asked questions

What is CVE-2025-31911 — SQL Injection in Social Share And Social Locker?

CVE-2025-31911 is a critical SQL Injection vulnerability affecting versions 0–1.4.2 of the Social Share And Social Locker WordPress plugin, allowing attackers to extract data via blind SQL injection.

Am I affected by CVE-2025-31911 in Social Share And Social Locker?

If your WordPress site uses Social Share And Social Locker version 0 through 1.4.2, you are vulnerable to this SQL Injection flaw. Upgrade immediately.

How do I fix CVE-2025-31911 in Social Share And Social Locker?

Upgrade the Social Share And Social Locker plugin to version 1.4.3 or later to resolve this vulnerability. If upgrading is not possible, temporarily disable the plugin.

Is CVE-2025-31911 being actively exploited?

As of now, there are no confirmed active exploitation campaigns targeting CVE-2025-31911, but the blind SQL injection nature makes exploitation possible.

Where can I find the official Social Share And Social Locker advisory for CVE-2025-31911?

Refer to the plugin developer's website or WordPress plugin repository for the official advisory and update information regarding CVE-2025-31911.

Is your project affected?

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.