Alipay <= 3.7.2 - Authenticated SQL Injection
Description
The WordPress支付宝Alipay plugin ≤3.7.2 has an unauthenticated SQL injection flaw in the proid parameter.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
The WordPress支付宝Alipay plugin ≤3.7.2 has an unauthenticated SQL injection flaw in the `proid` parameter.
Vulnerability
The WordPress Alipay|财付通Tenpay|贝宝PayPal集成插件 (Alipay plugin) up to version 3.7.2 contains a SQL injection vulnerability in the /includes/tpl.edit_product.php file at line 65. The proid parameter from the GET request is directly concatenated into a SQL query without sanitization, escaping, or quote delimiters, allowing injection of arbitrary SQL fragments [1]. The affected file is part of the plugin's administrative interface.
Exploitation
An attacker must have Administrator-level access to the WordPress admin panel [1]. The exploit is triggered via a crafted GET request to wp-admin/options-general.php?page=ws_alipay&action=edit&proid=... where the proid parameter contains a malicious payload such as -5818 UNION ALL SELECT ... user() ... # [1]. The provided proof-of-concept demonstrates a UNION-based injection that retrieves database user information [2]. No other privileges or interaction beyond administrator access is required.
Impact
Successful exploitation allows an authenticated administrator to extract arbitrary data from the WordPress database, including user credentials and other sensitive information. The example PoC retrieves the current database user via the user() function [1]. The injection could also be extended to modify or delete data, though the primary impact is information disclosure. The attacker achieves the same privilege level as the admin user but can exfiltrate data not normally visible through the admin interface.
Mitigation
As of the latest disclosure (July 2021), no fix has been released by the vendor [2]. The plugin remains unpatched, and users are advised to either remove or disable the plugin until a security update is provided. No workarounds have been formally published. The vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1- Range: <=3.7.2
Patches
0No patches discovered yet.
Vulnerability mechanics
Root cause
"The `proid` GET parameter is directly concatenated into a SQL query without sanitization, escaping, or validation, and the query is not delimited by quotes, allowing SQL injection."
Attack vector
An attacker with Administrator-level access sends a crafted GET request to `/wp-admin/options-general.php?page=ws_alipay&action=edit` with a malicious `proid` parameter containing a SQL injection payload [ref_id=1]. The parameter is not sanitised, escaped, or validated before being inserted into a SQL statement that is not delimited by quotes, allowing the attacker to execute arbitrary SQL commands [ref_id=1]. The exploit PoC demonstrates a UNION-based injection that extracts database information such as the database user [ref_id=1].
Affected code
The vulnerability resides in `/includes/tpl.edit_product.php` at line 65, where the `proid` GET parameter is directly interpolated into a SQL query without sanitization, escaping, or validation [ref_id=1]. The query is `"SELECT \`meta_key\`,\`meta_value\` FROM {$wpdb->wsaliproductsmeta} WHERE \`wsaliproducts_id\`={$_GET['proid']};"` [ref_id=1].
What the fix does
The advisory does not provide a patch diff or remediation code [ref_id=1]. To fix the vulnerability, the `proid` parameter must be properly sanitized, cast to an integer, or passed through a prepared statement with parameterized queries to prevent SQL injection. The advisory recommends that input validation and proper escaping should be applied to the `$_GET['proid']` value before it is used in the SQL query [ref_id=1].
Preconditions
- authAttacker must have Administrator-level access to the WordPress site
- configThe vulnerable plugin (WordPress支付宝Alipay|财付通Tenpay|贝宝PayPal集成插件) version 3.7.2 or lower must be installed and active
- networkAttacker must be able to send HTTP GET requests to the WordPress admin panel
Reproduction
Send a GET request to `/wp-admin/options-general.php?page=ws_alipay&action=edit&proid=-5818 UNION ALL SELECT 73,73,73,73,73,user(),73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73,73#` with a valid administrator session cookie [ref_id=1].
Generated on May 29, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
2- codevigilant.com/disclosure/2021/wp-plugin-alipay/mitrex_refsource_MISC
- wpscan.com/vulnerability/92b0abec-082f-4545-9636-1b2f4dac66femitrex_refsource_MISC
News mentions
0No linked articles in our index yet.