CVE-2021-47872: SEO Panel: blind SQLi via order_col in archive.php

HIGHPoC AVAILABLECISA: TRACK*

Published January 21, 2026

CISO Take

SEO Panel before 4.9.0 has a blind SQL injection in archive.php, where the 'order_col' parameter is passed unsanitized into database queries. An authenticated, low-privilege user can extract database contents with off-the-shelf tooling such as sqlmap, and a public exploit exists on Exploit-DB (49666), so the barrier to exploitation is low. The CVSS score is 7.1, with high confidentiality impact. EPSS data is unavailable and the CVE is not in CISA KEV, so there is no evidence of active exploitation. This is an SEO marketing tool rather than an AI/ML component, and its AI relevance is tenuous, but 516 downstream dependents and 81 other CVEs in the same package point to a weak security track record. Upgrade to 4.9.0 or later, restrict access to the panel, and review database credentials stored by the application.

Sources:NVDEPSSATLASOpenSSFVulnCheckExploit-DB

What is the risk?

Medium-high. The attack is network-reachable, low complexity, needs only low privileges and no user interaction, and a public exploit is documented. Impact is mostly confidentiality (credentials, API keys, stored data) with limited integrity impact. Exposure is limited by the authentication requirement. No KEV listing, no Nuclei template, and no EPSS data suggest low observed exploitation. The package has a history of vulnerabilities (81 other CVEs) and a mediocre OpenSSF Scorecard of 6.6/10.

How does the attack unfold?

Initial Access

Attacker authenticates to SEO Panel using a low-privilege or stolen account.

AML.T0012

Exploitation

Attacker injects SQL into the order_col parameter of archive.php using sqlmap to perform blind extraction.

AML.T0049

Collection

Attacker dumps database tables containing credentials, API keys, and project data.

AML.T0036

Impact

Stolen credentials and API keys are used to access connected AI services or pivot to other systems.

AML.T0055

Initial Access

Attacker authenticates to SEO Panel using a low-privilege or stolen account.

AML.T0012

Exploitation

Attacker injects SQL into the order_col parameter of archive.php using sqlmap to perform blind extraction.

AML.T0049

Collection

Attacker dumps database tables containing credentials, API keys, and project data.

AML.T0036

Impact

Stolen credentials and API keys are used to access connected AI services or pivot to other systems.

AML.T0055

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
Panel	pip	—	No patch
5.8KOpenSSF 6.6516 dependentsPushed 7d ago64% patched~15d to patchFull package profile →

Do you use Panel? You're affected.

How severe is it?

CVSS 3.1

7.1 / 10

EPSS

0.3%

chance of exploitation in 30 days

Higher than 19% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

Exploit Available

Exploitation: MEDIUM

Sophistication

Trivial

Exploitation Confidence

medium

○CISA SSVC: Public PoC

○Public PoC indexed (trickest/cve)

Composite signal derived from CISA KEV, VulnCheck KEV, CISA SSVC, EPSS, Metasploit, Exploit-DB, trickest/cve, Nuclei templates, and inthewild.io exploitation reports.

What is the attack surface?

AVNetwork

ACLow

PRLow

UINone

SUnchanged

CHigh

ILow

ANone

What should I do?

1 step

1) Upgrade SEO Panel to version 4.9.0 or later. 2) Until patched, restrict panel access by network (VPN or IP allowlist) and review the list of authenticated accounts. 3) Rotate any API keys and credentials stored in the SEO Panel database if exposure is suspected. 4) Add WAF rules to detect SQL injection patterns in the order_col parameter of archive.php. 5) Monitor web and database logs for sqlmap user agents, time-delay queries, and repeated requests to archive.php with unusual order_col values. 6) Run the database account with least privilege.

What does CISA's SSVC say?

DecisionTrack*

Exploitationpoc

AutomatableNo

Technical Impactpartial

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Data ExtractionData LeakageFrameworkAPIAML.T0049- Exploit Public-Facing Application AML.T0055- Unsecured Credentials

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001

A.6.2.6-AI system operation and monitoring

NIST AI RMF

MANAGE 2.3-Responding to identified risks

OWASP LLM Top 10

LLM05-Supply Chain Vulnerabilities

Frequently Asked Questions

What is CVE-2021-47872?

Is CVE-2021-47872 actively exploited?

Proof-of-concept exploit code is publicly available for CVE-2021-47872, increasing the risk of exploitation.

How to fix CVE-2021-47872?

1) Upgrade SEO Panel to version 4.9.0 or later. 2) Until patched, restrict panel access by network (VPN or IP allowlist) and review the list of authenticated accounts. 3) Rotate any API keys and credentials stored in the SEO Panel database if exposure is suspected. 4) Add WAF rules to detect SQL injection patterns in the order_col parameter of archive.php. 5) Monitor web and database logs for sqlmap user agents, time-delay queries, and repeated requests to archive.php with unusual order_col values. 6) Run the database account with least privilege.

What systems are affected by CVE-2021-47872?

This vulnerability affects the following AI/ML architecture patterns: Web-based ML UI / management dashboards, AI-assisted content generation workflows, Marketing automation pipelines.

What is the CVSS score for CVE-2021-47872?

CVE-2021-47872 has a CVSS v3.1 base score of 7.1 (HIGH). The EPSS exploitation probability is 0.27%.

What is the AI security impact?

Affected AI Architectures

Web-based ML UI / management dashboardsAI-assisted content generation workflowsMarketing automation pipelines

MITRE ATLAS Techniques

AML.T0049Exploit Public-Facing Application

AML.T0055Unsecured Credentials

Compliance Controls Affected

ISO 42001: A.6.2.6

NIST AI RMF: MANAGE 2.3

OWASP LLM Top 10: LLM05

What are the technical details?

Original Advisory

SEO Panel versions prior to 4.9.0 contain a blind SQL injection vulnerability in the archive.php page that allows authenticated attackers to manipulate database queries through the 'order_col' parameter. Attackers can use sqlmap to exploit the vulnerability and extract database information by injecting malicious SQL code into the order column parameter.

Exploitation Scenario

An attacker obtains a low-privilege account on an exposed SEO Panel instance through credential stuffing or a self-registered account. They run sqlmap against archive.php, injecting into the order_col parameter to perform time-based or boolean blind extraction. They dump the user table, password hashes, and stored API keys for third-party services, including LLM or content-generation APIs. They then use those keys to abuse AI services at the victim's expense or to pivot into connected systems.

Weaknesses (CWE)

CWE-89Improper Neutralization of Special Elements used in an SQL Command

CWE-89 — Improper Neutralization of Special Elements used in an SQL Command: The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

[Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.
[Architecture and Design] If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated. Process SQL queries using prepared statements, parameterized queries, or stored procedures. These features should accept parameters or variables and support strong typing. Do not dynamically construct and execute query strings within these features using "exec" or similar functionality, since this may re-introduce the possibility of SQL injection. [REF-867]

Source: MITRE CWE corpus.