dbcve.org
Add To Cart Text Changer And Customize Button\, Add Custom IconWordPress extension · Codeastrology

CVE-2023-49153

HIGH · 8.8 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to after 2.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Saiful Islam Add to Cart Text Changer and Customize Button, Add Custom Icon.This issue affects Add to Cart Text Changer and Customize Button, Add Custom Icon: from n/a through 2.0.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WordPress plugin 'Add to Cart Text Changer and Customize Button, Add Custom Icon' allows attackers to induce authenticated users to perform unwanted actions (such as modifying button text/customization settings) by tricking them into submitting malicious requests. The plugin lacks proper CSRF token validation on its administrative functions.

MitigationImplement WordPress nonces on all form submissions and AJAX requests within the plugin, and verify these nonces before processing any administrative actions. Ensure nonce verification is applied to all state-changing operations.

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
Add To Cart Text Changer And Customize Button\, Add Custom IconWordPress extension
Affected:<= 2.0

CVSS 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the vulnerable plugin is installed
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the wp-content/plugins directory for a plugin named 'Add to Cart Text Changer And Customize Button' or 'Codeastrology Add To Cart Text Changer And Customize Button'
    Affected if The plugin appears in the list of installed plugins
  2. Check the installed version
    In the WordPress admin, find the plugin in the Plugins list and view the version number displayed beneath the plugin name, or inspect the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The version number is 2.0 or lower (e.g., 2.0, 1.9, 1.8, etc.)
  3. Verify CSRF protection in plugin administrative functions
    Examine the plugin's PHP source code (typically found in wp-content/plugins/ directory under the plugin folder) and search for nonce verification functions such as wp_verify_nonce, check_admin_referer, or wp_nonce_field in all form handling and AJAX request handlers
    Affected if No nonce verification functions are found in the plugin's admin action handlers, or the verification is missing before processing state-changing operations
  4. Check plugin settings pages for CSRF protection
    Access the plugin's settings page in WordPress admin (typically under WooCommerce or Settings menu) and inspect any forms or AJAX calls. Use browser developer tools to examine form submissions for the presence of a nonce field (usually named '_wpnonce' or similar)
    Affected if Forms submitted from the plugin settings pages do not include a valid nonce token

A user is affected if the plugin is installed with version 2.0 or lower and the plugin's admin functions lack proper nonce verification for CSRF protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.0
Interim mitigation

Implement WordPress nonces on all form submissions and AJAX requests within the plugin, and verify these nonces before processing any administrative actions. Ensure nonce verification is applied to all state-changing operations.

Fix this in Add To Cart Text Changer And Customize Button\, Add Custom Icon Scoped from the published advisory
  • Consultation1.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,220
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,952.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49153 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-49153 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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