Affiliate For WoocommerceWordPress extension · Storeapps
CVE-2022-36284
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 · uneditedAuthenticated IDOR vulnerability in StoreApps Affiliate For WooCommerce premium plugin <= 4.7.0 at WordPress allows an attacker to change the PayPal email. WooCommerce PayPal Payments plugin (free) should be at least installed to get the extra input field on the user profile page.
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 confidenceAuthenticated IDOR vulnerability in StoreApps Affiliate For WooCommerce premium plugin <= 4.7.0 allows authenticated attackers to modify PayPal email addresses of other users due to missing authorization validation on the user profile field. The vulnerability is exploitable when WooCommerce PayPal Payments plugin is installed, exposing an extra input field that can be tampered with via direct object reference.
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
Affiliate For WoocommerceWordPress extension
<= 4.7.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Verify StoreApps Affiliate For WooCommerce is installedCheck your WordPress plugins directory or WordPress admin panel for the StoreApps Affiliate For WooCommerce plugin listingAffected if The plugin is present in the installation
-
Check the installed version of StoreApps Affiliate For WooCommerceView the plugin version in the WordPress plugin admin page or inspect the plugin header in its main PHP fileAffected if The installed version is 4.7.0 or lower
-
Confirm WooCommerce PayPal Payments plugin is installedCheck your WordPress plugins list for the WooCommerce PayPal Payments pluginAffected if The WooCommerce PayPal Payments plugin is installed and active
-
Identify if PayPal email field is exposed in user profilesNavigate to a user profile page in WordPress admin and look for a PayPal email address input field that appears when WooCommerce PayPal Payments is activeAffected if The PayPal email field is visible and accessible in user profile pages
-
Test authorization on user profile modificationAs an authenticated user with limited privileges, attempt to modify the PayPal email address of a different user account via direct parameter manipulation or profile editingAffected if You are able to successfully modify another user's PayPal email address without proper authorization
Your environment is affected if StoreApps Affiliate For WooCommerce version 4.7.0 or lower is installed alongside the WooCommerce PayPal Payments plugin, exposing a modifiable PayPal email field that can be altered for other users without authorization.
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 StoreApps Affiliate For WooCommerce to a version beyond 4.7.0. If no patch is available, implement server-side authorization checks to ensure users can only modify their own PayPal email addresses, and validate the user ID matches the authenticated session.
Fix this in Affiliate For Woocommerce
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-2022-36284 — 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-36284 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