Unauthenticated SQL injection via p_id and read
Published Sep 18, 2026 · Updated Sep 18, 2026
SQL injection in Product Question and Answer through 1.1.0 allows remote attackers to extract sensitive data via public AJAX actions. The AJAX handlers pass untrusted p_id and read request parameters into SQL queries without sanitizing or escaping them. No account is required, and the reported consequence is sensitive-data extraction from the WordPress database.
Summary
What happened
SQL injection in Product Question and Answer through 1.1.0 allows remote attackers to extract sensitive data via public AJAX actions. The AJAX handlers pass untrusted p_id and read request parameters into SQL queries without sanitizing or escaping them. No account is required, and the reported consequence is sensitive-data extraction from the WordPress database.
The record
- CVE
- CVE-2026-87771
- Published
- Sep 18, 2026
- Updated
- Sep 18, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started