Skip to content
LatestProtect Android accounts: New features blank payment screens and warn before call forwarding activates
Vulnerabilities

Update Stylemix uListing to Fix Critical SQLi Allowing Remote Code Execution in Versions Up to 2.2.0

The NVD rates CVE-2026-62031 as critical, noting that unauthenticated SQL injection flaws in Stylemix uListing versions up to 2.2.0 allow remote attackers to execute arbitrary code.

Illustration: A cracked smartphone screen displays abstract blue glitch shapes against a dark background.
AI-generated illustration: DarkWeb Headlines

Key points

  • The National Vulnerability Database assigned CVE-2026-62031 a CVSS score of 9.3, categorizing the flaw as critical.
  • The vulnerability affects Stylemix uListing plugin versions 2.2.0 and all earlier releases.
  • The security issue is classified as an unauthenticated SQL injection, corresponding to CWE-89.

The National Vulnerability Database (NVD) has published a critical security advisory for the Stylemix uListing plugin, identifying a severe flaw in versions up to 2.2.0. The record, designated CVE-2026-62031, describes an unauthenticated SQL injection vulnerability that could allow remote attackers to compromise database integrity. Security teams must prioritize this finding due to the high CVSS score and the lack of authentication requirements for exploitation.

Root cause

The underlying issue stems from improper input validation within the plugin’s codebase, specifically related to how it processes SQL queries. According to the NVD record, the weakness aligns with CWE-89, which covers SQL injection flaws. This classification indicates that the application fails to neutralize special elements in user-supplied data before sending them to the SQL database. Consequently, attackers can manipulate these inputs to alter the intended logic of the query.

Attack path

An attacker can exploit this vulnerability without needing valid credentials or prior access to the application. The term "unauthenticated" in the NVD description confirms that the flaw is accessible to anyone on the internet who can reach the affected server. By injecting malicious SQL code into input fields or parameters, the attacker can execute arbitrary commands against the database. This path allows for potential data exfiltration, modification, or complete system takeover.

Affected versions

The vulnerability impacts a specific range of the Stylemix uListing plugin. The NVD record explicitly states that versions up to and including 2.2.0 are affected. This means that any installation running version 2.2.0 or any earlier release contains the unauthenticated SQL injection flaw. Organizations using these versions are exposed to the risk described in CVE-2026-62031 until they apply a remediation.

Mitigation

  • Verify the current version of the Stylemix uListing plugin installed on your WordPress sites.
  • Check if your version is 2.2.0 or lower, as these are confirmed to be vulnerable.
  • Monitor vendor communications for an official patch that addresses CVE-2026-62031.
  • Restrict access to the application backend where possible to reduce exposure.

What to do and how to stay safe: Stylemix

  • Audit your WordPress installations to identify any sites using the Stylemix uListing plugin.
  • Check the version number of the plugin against the affected range of up to 2.2.0.
  • Review web server logs for unusual database query patterns that may indicate exploitation.
  • Prepare to update the plugin immediately once the vendor provides a secure version.

Step-by-step guide: Vulnerability Management Definition and Process

General security guidance from the DarkWeb Headlines newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is the CVSS score for CVE-2026-62031?

The National Vulnerability Database assigns a CVSS score of 9.3 to this vulnerability, rating it as critical.

Which versions of Stylemix uListing are affected?

All versions of the Stylemix uListing plugin up to and including version 2.2.0 are affected by this flaw.

Does an attacker need login credentials to exploit this bug?

No, the NVD describes the vulnerability as unauthenticated, meaning no credentials are required for exploitation.

Sources

  1. CVE Program
StylemixuListingCVE-2026-62031SQL InjectionWordPress

Related stories

Patch phpMyFAQ Immediately to Fix Critical SQL Injection in Autocomplete API

Unauthenticated attackers can exploit CVE-2026-109573 in phpMyFAQ versions prior to 4.1.9 to steal credentials and modify database records through a flawed escape mechanism.