PXLSecurity LTD., Sofia, Bulgaria Offensive security since 2014[email protected]

CVE-2024-0566

Smart Manager for WordPress SQL injection

Insufficient escaping of a parameter leads to SQL injection via a high-privilege role.

SQL injectionHigh

Technical summary

Smart Manager is a WordPress and WooCommerce bulk-editing plugin. It uses a request parameter in an SQL statement without sanitising or escaping it first.

The published vector puts privileges required at high: the issue is reachable from an administrator-level account. That still matters, because it turns a restricted administrative interface into arbitrary database access and widens the blast radius of any single compromised or over-provisioned admin login.

Impact

Arbitrary read and write access to the WordPress database from an administrative account, beyond the operations the plugin interface exposes.

The Smart Manager WordPress plugin before 8.28.0 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privilege users such as admin.

Remediation

WPScan records the issue as fixed in Smart Manager 8.28.0.

Published severity

Published byVersionBase scoreVector
NVDCVSS 3.1 7.2 High CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CISA-ADPCVSS 3.1 7.2 High CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

More than one organisation has scored this issue. We reproduce every published score and vector as published, attributed to its source, and do not compute our own.

Disclosure timeline

  1. 2024-01-18WPScan advisory published
  2. 2024-02-12CVE record published

Only publicly documented dates are shown. Where a step in the process was not published, it is not listed.

References

Credit

Researcher: Ivan Spiridonov

Credited as finder in the CVE record and on the WPScan advisory; WPScan is recorded as the coordinator.

This is the work we do commercially

Vulnerability research and penetration testing by the same engineers who found this issue. Every report carries reproduction steps, impact and a retest.

We publish advisories, not exploits. Each entry describes the vulnerability class and impact at the level the vendor advisory does, and links to the authoritative records. Where public proof-of-concept code exists we link to it rather than reproduce it.

How we disclose

Every issue here was reported to the vendor or to a coordinating programme before publication. We publish only once a fix is available or the coordinated disclosure window has elapsed.

Want this kind of scrutiny on your own software?

Tell us what you want to protect. A senior tester will help you agree the scope and next steps. We usually reply within one business day.

Confidential from the first conversation

We can sign your NDA before you share sensitive details. Your enquiry is covered by our privacy policy.

How we protect your information · Privacy policy