SQL Injection in WP Crowdfunding (WordPress plugin) (CVE-2026-19944)
Summary
SQL injection in WP Crowdfunding (WordPress plugin) (CVE-2026-19944). Confidential information can be exposed externally. Exploitable via PUT /wp-json/wc/v3/products/{id}.
Original description
The description as published by the source.
The WP Crowdfunding plugin for WordPress is vulnerable to generic SQL Injection via 'wpneo_reward' Post Meta in all versions up to, and including, 2.2.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 shop manager-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is a second-order injection: a Shop Manager writes the malicious payload once via the WooCommerce REST products endpoint (POST/PUT /wp-json/wc/v3/products/{id}), and the injected query executes on every subsequent public page view that renders the campaign rewards sidebar.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-19944 has been found in WP Crowdfunding (WordPress plugin).
Attackers can target a specific entry point like PUT /wp-json/wc/v3/products/{id} over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 4.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WP Crowdfunding (WordPress plugin) CVE-2026-19944" on the vendor's site.
CVE-2026-19944 (WP Crowdfunding (WordPress plugin)) — CWE-89 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /wp-json/wc/v3/products/{id}
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in WP Crowdfunding (WordPress plugin). Attackers reach the vulnerable code path via PUT /wp-json/wc/v3/products/{id}.
Check the vendor advisory for the affected versions of WP Crowdfunding (WordPress plugin). Attack surface: PUT /wp-json/wc/v3/products/{id}.
Severity: Medium (CVSS 4.9/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /wp-json/wc/v3/products/{id} requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで WP Crowdfunding (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'PUT /wp-json/wc/v3/products/{id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /wp-json/wc/v3/products/{id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PUT /wp-json/wc/v3/products/{id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。