CVE-2025-47648
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 axima Pays – WooCommerce Payment Gateway axima-payment-gateway allows Stored XSS.This issue affects Pays – WooCommerce Payment Gateway: from n/a through <= 2.6.
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 confidenceCSRF vulnerability in the axima-payment-gateway WordPress plugin allows attackers to trick authenticated administrators into submitting malicious requests, leading to stored XSS. The lack of proper CSRF protection and input validation enables injection of arbitrary scripts into the plugin settings that execute when viewed by other users.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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.
-
Verify axima-payment-gateway plugin is installedNavigate to WordPress admin > Plugins and look for 'axima-payment-gateway' in the installed plugins listAffected if Plugin is present in the plugins directory
-
Check installed plugin versionIn the Plugins list, click on 'Plugin details' or view the plugin header file to find the Version fieldAffected if Version is 2.6 or lower
-
Inspect plugin settings forms for CSRF protectionNavigate to the plugin settings page (typically under WooCommerce > Payment Gateways or a dedicated axima settings menu). Use browser developer tools to inspect form elements, looking for any CSRF token, nonce, or token fields in the form markupAffected if No CSRF token or nonce field is present in the plugin settings forms
-
Review plugin settings for injected scriptsExamine all configuration fields in the plugin settings panel for any unexpected script tags, event handlers (onclick, onerror, etc.), or suspicious JavaScript code that may have been storedAffected if Plugin settings contain arbitrary script tags or JavaScript that was injected without proper sanitization
If the plugin is installed with version 2.6 or below and the settings forms lack CSRF token implementation, the environment is affected by this CSRF-to-stored-XSS vulnerability
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 axima-payment-gateway plugin to the latest version beyond 2.6, which should include CSRF token implementation and proper input sanitization. Until then, disable the plugin or restrict admin access.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47648 — 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-2025-47648 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