SEO Panel SQL injection in Site Auditor component
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
SEO Panel's Site Auditor component has an SQL injection flaw in its order_col and order_val arguments. A remote attacker with a low-privilege login can exploit it over the network to inject SQL commands into database queries.
Written by a model
Original description
A flaw has been found in SEO Panel 6.0.0. Affected is an unknown function of the file controllers/siteauditor.ctrl.php of the component Site Auditor. Executing a manipulation of the argument order_col/order_val can lead to sql injection. The attack can be launched remotely. The exploit has been published and may be used. Upgrading to version 7.0.0 is able to address this issue. This patch is called 2a2d4aeb718177327b0cd8ce17e2f40328772127. It is suggested to upgrade the affected component.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132603 (SEO Panel Site Auditor siteauditor.ctrl.php sql injection), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132603 (entry last updated 2026-11-19):
Affected:
- n/a SEO Panel: versions 6.0.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132603 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132603 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/seopanel/Seo-Panel/commit/2a2d4aeb718177327b0cd8ce17e2f40328772127
- https://github.com/seopanel/Seo-Panel/releases/tag/7.0.0
- https://vuldb.com/vuln/439703
- https://vuldb.com/vuln/439703/cti
- https://vuldb.com/cve/CVE-2026-132603
- https://vuldb.com/submit/1045075
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132603
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132603"}.Affected versions
- n/a SEO Panel6.0.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 9
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132603 |
| Record | NVD · CVE-2026-132603 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · Leousum/VulnPoC · Seo-Panel_6.0.0/siteauditor_duplicatemeta_sql_injection.md |
| Other links 6 | |
| Advisory | VulDB · Advisory #439703 |
| Advisory | VulDB · Threat intelligence #439703 |
| Advisory | VulDB · CVE-2026-132603 record |
| Advisory | VulDB · Submission #1045075 |
| Patch | GitHub · seopanel/Seo-Panel · Commit 2a2d4aeb |
| Patch | GitHub · seopanel/Seo-Panel · Release 7.0.0 |
Questions about CVE-2026-132603
Is CVE-2026-132603 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-132603?
SEO Panel: version 6.0.0.
Source: cve.now feed data
Related
- CVE-2026-87977IBM Guardium Data Protection SQL Injection
- CVE-2026-129411Joomla Extension - vi-solutions - Unauthenticated SQL injection in frontend data view filters in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1
- CVE-2026-133534Neotroni Lighting|PowerLink - SQL Injection
- CVE-2026-93911Dimension SQL Injection in Log Collector Allows Remote Code Execution
- CVE-2026-129412Joomla Extension - vi-solutions - SQL injection in backend data search and export in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1
- CVE-2026-122676WordPress PublishPress Authors plugin <= 4.18.0 - SQL Injection vulnerability
No corrections so far. Something wrong on this page? Report an error.