Button GeneratorWordPress extension · Wow Company
CVE-2023-49155
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Wow-Company Button Generator – easily Button Builder.This issue affects Button Generator – easily Button Builder: from n/a through 2.3.8.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability exists in the Wow-Company Button Generator plugin for WordPress (versions up to 2.3.8). The plugin fails to properly validate the origin of requests, allowing attackers to trick authenticated administrators into submitting unintended requests—such as creating, modifying, or deleting button configurations—via social engineering or malicious links.
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
Button GeneratorWordPress extension
<= 2.3.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'Wow Company Button Generator' or check the /wp-content/plugins/ directory for a folder containing 'wow' and 'button-generator' in the nameAffected if The plugin is installed and active
-
Check installed versionIn WordPress admin, go to Plugins > Installed Plugins, find the Wow Company Button Generator plugin, and note the version number displayedAffected if Version is 2.3.8 or lower
-
Inspect form submissions for nonce validationExamine the plugin's PHP files in wp-content/plugins/ for form handling code (look for admin-post.php, wp_ajax actions, or form tags). Search for presence of wp_nonce_field, wp_verify_nonce, or check_admin_referer functions in the plugin's AJAX and form handlersAffected if No nonce verification is found in form submission handlers or AJAX endpoints
-
Verify SameSite cookie configurationCheck the plugin's cookie-setting code for SameSite attribute on session or preference cookies, or inspect HTTP response headers when admin pages loadAffected if Cookies lack SameSite=Strict or SameSite=Lax attributes
If the plugin is installed and the version is 2.3.8 or lower, and no nonce validation is found in form handlers, the environment is vulnerable to CVE-2023-49155.
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 dataUpdate the plugin to the latest version which implements anti-CSRF token validation (WordPress nonces) for all form submissions and AJAX requests, and configure SameSite cookie attributes.
Fix this in Button Generator
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49155 — 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-2023-49155 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