Radar sectionsDatabase
Check my site
WordPress plugin

XPlainer — WooCommerce Product FAQ <= 1.6.3 - Reflected Cross-Site Scripting

CVE-2024-37515Published · Updated

Action summary

Affected: ≤1.6.3Update to 1.6.4 or newer

All remediation steps
Severity
Medium6.1
CVSS
6.1
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:R User interaction
Required
S:C Scope
Changed
C:L Confidentiality
Low
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-79 Cross-Site Scripting
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Happy FAQs – FAQ, Product FAQ & Help Center faq-for-woocommerce

  1. Affected≤ 1.6.3
  2. Patched in1.6.4

Update to 1.6.4 or newer.

You are affected if you run ≤ 1.6.3. Version 1.6.4 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Happy FAQs – FAQ, Product FAQ & Help Center.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 1.6.4, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Happy FAQs – FAQ, Product FAQ & Help Center to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to LVT-tholv2k.

The XPlainer – WooCommerce Product FAQ [WooCommerce Accordion FAQ Plugin plugin for WordPress is vulnerable to Reflected Cross-Site Scripting in all versions up to, and including, 1.6.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Happy FAQs – FAQ, Product FAQ & Help Center

All 5
More vulnerabilities in Happy FAQs – FAQ, Product FAQ & Help Center
SeverityVulnerabilityCVEPublished
Medium6.4Missing Authorization to Authenticated (Subscriber+) Stored Cross-Site Scripting
≤1.7.0Update to 1.7.1
CVE-2024-5669
Medium4.3Missing Authorization to Authenticated (Subscriber+) Settings Update
≤1.7.0Update to 1.7.1
CVE-2024-5704
Medium4.3Missing Authorization via handle_optin_optout
≤4.1.2Update to 4.1.3
CVE-2024-32110
Medium6.1Reflected Cross-Site Scripting via fs_request_get
≤1.9.2No patch available
CVE-2023-33999

Same weakness (Cross-Site Scripting)

All Cross-Site Scripting
Other Cross-Site Scripting vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity medium, CVSS 6.1

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?