Wp Full Stripe FreeWordPress extension · Paymentsplugin
CVE-2023-47667
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 Mammothology WP Full Stripe Free.This issue affects WP Full Stripe Free: from n/a through 7.0.16.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP Full Stripe Free WordPress plugin (versions through 7.0.16) allows attackers to trick authenticated administrators into performing unintended actions such as modifying Stripe payment configuration, creating/changing subscriptions, or altering plugin settings.
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
Wp Full Stripe FreeWordPress extension
<= 1.6.1CVSS 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.
-
Confirm WP Full Stripe Free plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WP Full Stripe Free' or 'Wp Full Stripe Free' in the plugin listAffected if Plugin is not found in the installed plugins list
-
Identify the installed plugin versionClick on the plugin name in the plugins list to view its details, or check the plugin header in /wp-content/plugins/wp-full-stripe-free/ folder for the Version fieldAffected if Installed version is at or below 7.0.16 (or 1.6.1 if using a different versioning scheme)
-
Verify the plugin is activeIn the Plugins admin page, check if WP Full Stripe Free shows as 'Active' under the plugin status columnAffected if Plugin is active and processing Stripe payment forms or admin actions
-
Confirm admin user access existsCheck Users > All Users in WordPress admin for at least one user with Administrator roleAffected if An authenticated administrator session exists, which is required for the CSRF attack to be triggered
You are affected if WP Full Stripe Free is installed, active, running version 7.0.16 or below, and has at least one administrator user account that could be tricked into submitting a forged request.
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 WP Full Stripe Free to the latest patched version. If no update is available, implement WordPress nonces (anti-CSRF tokens) on all form submissions and state-changing actions within the plugin.
Fix this in Wp Full Stripe Free
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-47667 — 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-47667 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