CVE-2026-22382
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 Mikado-Themes PawFriends - Pet Shop and Veterinary WordPress Theme pawfriends allows Cross Site Request Forgery.This issue affects PawFriends - Pet Shop and Veterinary WordPress Theme: from n/a through <= 1.3.
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 PawFriends WordPress theme allows attackers to trick authenticated users into performing unintended actions (such as modifying settings or making purchases) by leveraging the site's trust in the user's browser. The theme lacks proper anti-CSRF token validation on state-changing requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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.
-
Identify if PawFriends theme is installedIn WordPress admin dashboard, go to Appearance > Themes and check if the PawFriends theme is listed and active. Alternatively, check the wp-content/themes directory for a folder named 'pawfriends' or similar.Affected if The PawFriends theme is installed and active on the WordPress site
-
Locate theme files containing forms and AJAX handlersAccess the theme directory via file manager or FTP. Look for PHP files that contain form tags (form), AJAX actions (wp_ajax), or state-changing functionality such as settings updates, user submissions, or purchase processing.Affected if The theme contains form handling or AJAX PHP files that process user requests
-
Verify presence of nonce verification in form handlersOpen the theme's PHP files that handle form submissions. Search for 'wp_verify_nonce' or 'check_admin_referer' functions immediately before any database write, settings update, or user action processing. Compare against the form rendering to ensure a matching nonce field (wp_nonce_field) was included.Affected if No nonce verification function (wp_verify_nonce, check_admin_referer, wp_nonce_field) is found before state-changing operations in the theme's PHP files
-
Inspect AJAX action handlers for CSRF protectionSearch the theme files for 'add_action' calls registering wp_ajax_ hooks. For each handler, verify that a nonce check is performed using wp_verify_nonce or check_ajax_referer before processing the request.Affected if AJAX handlers exist but lack nonce validation before processing requests
-
Check for Origin or Referer header validation on sensitive requestsReview the theme's PHP code handling administrative or user-account actions. Look for server-side validation of $_SERVER['HTTP_ORIGIN'] or $_SERVER['HTTP_REFERER'] to verify the request originated from the legitimate site.Affected if No Origin or Referer header validation is performed on sensitive actions
A site is affected if the PawFriends theme is active and its PHP code lacks wp_verify_nonce or check_admin_referer calls before processing state-changing requests from forms or AJAX endpoints.
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 dataImplement anti-CSRF tokens (nonces) on all forms and AJAX actions within the theme, verify Origin/Referer headers on sensitive requests, and utilize SameSite cookie attributes. Consider applying any vendor security patches if available.
- 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-2026-22382 — 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-2026-22382 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