mediumCVE-2026-15458

SEO Booster <= 7.3.1 - Authenticated (Administrator+) SQL Injection via 'sort_field' Parameter

Q: What is affected by CVE-2026-15458?

SEO Booster versions listed as affected should be reviewed: *-7.3.1.

Q: What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

Q: How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

The SEO Booster plugin for WordPress is vulnerable to generic SQL Injection via the 'sort_field' parameter in all versions up to, and including, 7.3.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

ProductSEO Booster

CVSS4.9

EPSSNot scored yet

UpdatedJuly 16, 2026

Quick answer

SEO Booster should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

*-7.3.1

Fixed versions

7.3.2

How to fix it

SEO Booster is affected by this security issue. The safest fix is to update to the fixed version, then test the site or service again to make sure the risky path is closed.

Find every place where SEO Booster is installed or used.
Update to 7.3.2 or a later vendor-supported version.
Back up the site or service before changing production systems.
Apply the update in staging first if possible, then deploy it to production.
If you cannot update right away, restrict access to the affected feature and monitor logs closely.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm the installed version or configuration is no longer in the affected range.
Retest the affected page, API, plugin, workflow, or network path.
Check logs after the change for blocked attempts, crashes, or errors.
Run a fresh Fixnx scan and save the report.

Related categories

WordPress SQL Injection Information Disclosure

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-15458?

SEO Booster versions listed as affected should be reviewed: *-7.3.1.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.