Acl Floating Cart For WoocommerceWordPress extension · Amadercode
CVE-2024-49640
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in AmaderCode Lab ACL Floating Cart for WooCommerce acl-floating-cart-for-woocommerce allows Reflected XSS.This issue affects ACL Floating Cart for WooCommerce: from n/a through <= 0.9.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceReflected XSS vulnerability in ACL Floating Cart for WooCommerce plugin (versions <= 0.9) allows attackers to inject malicious JavaScript via unsanitized input that gets reflected in web pages. The vulnerability occurs during web page generation where user-supplied data is not properly neutralized before output.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Acl Floating Cart For WoocommerceWordPress extension
<= 0.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check ACL Floating Cart plugin versionNavigate to WordPress admin > Plugins > Installed Plugins and locate 'ACL Floating Cart for WooCommerce', or check the plugin's main PHP file header for the Version fieldAffected if The displayed version is 0.9 or any version number lower than 0.9
-
Verify plugin is activeIn WordPress admin > Plugins, confirm the plugin status shows as 'Active'Affected if The plugin is enabled and running on the site
-
Confirm WooCommerce is installedCheck WordPress plugins list for WooCommerce or look for WooCommerce-specific functionality on the site storefrontAffected if WooCommerce is installed and the vulnerable plugin depends on it to render the affected cart functionality
-
Identify if plugin renders on storefront pagesVisit the site frontend, particularly cart, checkout, and product pages, and view page source to see if ACL Floating Cart code is present in the HTML outputAffected if The plugin JavaScript or HTML elements are present in the rendered storefront pages where user-supplied data could be reflected
If the ACL Floating Cart for WooCommerce plugin version is 0.9 or lower and the plugin is active on a WooCommerce site, the environment is likely affected by this reflected XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade ACL Floating Cart for WooCommerce to the latest version and implement proper input sanitization and output encoding for all user-supplied parameters in the affected plugin code.
Fix this in Acl Floating Cart For Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-49640 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data