Wp EasypayWordPress extension · Wpeasypay
CVE-2022-47177
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 WP Easy Pay WP EasyPay – Square for WordPress plugin <= 4.1 versions.
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 WP Easy Pay – Square for WordPress plugin versions 4.1 and below allows attackers to trick authenticated users into performing unintended actions by forcing their browser to send malicious requests.
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 EasypayWordPress extension
<= 4.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.
-
Verify WP Easy Pay plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Easy Pay - Square' or 'Wpeasypay Wp Easypay', or check the /wp-content/plugins/ directory for the plugin folder.Affected if Plugin is not installed or not found in the WordPress environment
-
Check installed plugin versionIn WordPress admin > Plugins > Installed Plugins, click on the plugin to view details and note the version number, or inspect the plugin's main PHP file header for the 'Version' tag.Affected if Version displayed is 4.1 or lower (e.g., 4.1, 4.0, 3.9, etc.)
-
Identify plugin forms and AJAX endpointsReview the plugin files in /wp-content/plugins/ for HTML form elements (especially in admin settings pages) and AJAX handlers registered via wp_ajax_ hooks.Affected if Plugin creates payment forms, settings forms, or AJAX endpoints that handle sensitive operations
-
Inspect forms for anti-CSRF tokens (nonces)Open the plugin's PHP files containing form definitions and search forwp_nonce_field, wp_nonce_url, or check_admin_referer function calls within the form rendering code.Affected if Forms lack nonce field generation (wp_nonce_field) or do not verify nonces upon submission
-
Inspect AJAX handlers for nonce verificationSearch plugin PHP files for wp_ajax_ hooks and verify the handler function includes check_ajax_referer or wp_verify_nonce before processing the request.Affected if AJAX endpoints do not call check_ajax_referer or wp_verify_nonce to validate the request origin
Environment is affected if the WP Easy Pay - Square plugin is installed with version 4.1 or lower AND the plugin's forms or AJAX endpoints lack nonce (anti-CSRF token) verification.
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 beyond 4.1 and implement anti-CSRF tokens (nonces) on all forms and AJAX endpoints, including proper referer/origin header validation.
Fix this in Wp Easypay
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47177 — 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-2022-47177 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