Script execution via unsanitized AJAX term identifier
Published Jan 16, 2024 · Updated Jun 11, 2025
Reflected XSS in BeRocket Advanced AJAX Product Filters before 1.5.4.7 allows remote attackers to execute script via a crafted term_id. The public br_aapf_get_child AJAX action returns the POST term_id value in its HTML response without sanitization or output encoding. An attacker needs no account but must induce a user to submit the crafted request; execution occurs in that user's browser under the affected site's origin.
Summary
What happened
Reflected XSS in BeRocket Advanced AJAX Product Filters before 1.5.4.7 allows remote attackers to execute script via a crafted term_id. The public br_aapf_get_child AJAX action returns the POST term_id value in its HTML response without sanitization or output encoding. An attacker needs no account but must induce a user to submit the crafted request; execution occurs in that user's browser under the affected site's origin.
The record
- CVE
- CVE-2021-24432
- Published
- Jan 16, 2024
- Updated
- Jun 11, 2025
- Vendor
- BeRocket
- Product
- Advanced AJAX Product Filters
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2024CVE publishedPublication date reported by the CVE source.
- Jun 11, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.5.4.7
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- WPScan proof-of-concept form and POST requestproof of concept · validated
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo