CVE-2021-24461

FAQ Builder AYS <= 1.3.5 - Blind SQL Injection

2021-06-29 00:00

Strategic Overview

Status: Patched in 1.3.6
Affected Plugin: FAQ Builder AYS
Affected Version: <= 1.3.5
CVSS: 8.8High
Weakness type: CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE: CVE-2021-24461

View all FAQ Builder AYS vulnerabilities

At a glance

CVE-2021-24461 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the FAQ Builder AYS WordPress plugin, affecting versions <= 1.3.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.3.6; sites on affected versions should update now. Disclosed June 2021, reported by To Quang Duong.

Vulnerability Overview

The get_faqs() function in the FAQ Builder AYS WordPress plugin before 1.3.6 did not use whitelist or validate the orderby parameter before using it in SQL statements passed to the get_results() DB calls, leading to SQL injection issues in the admin dashboard

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

FAQ Builder AYS <= 1.3.5 carries this weakness at get_faqs(), and reaching it takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For FAQ Builder AYS the fix is 1.3.6: builds <= 1.3.5 are affected, anything from 1.3.6 onward is not.

Remediation

Update to version 1.3.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to FAQ Builder AYS: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: FAQ Builder AYS 1.3.6 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-24461 https://www.wordfence.com/threat-intel/vulnerabilities/id/c0a2a379-bd33-4c7d-8b79-e48a2df7e281 https://nvd.nist.gov/vuln/detail/CVE-2021-24461

Related records

Other vulnerabilities in FAQ Builder AYS

CVSS Vector

8.8

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/