CVE-2025-31906
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 ProfitShare.ro WP Profitshare wp-profitshare allows Stored XSS.This issue affects WP Profitshare: from n/a through <= 1.4.9.
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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP Profitshare WordPress plugin allows authenticated administrators to be tricked into performing unintended actions that inject malicious JavaScript (Stored XSS). An attacker crafts a malicious link or form that, when clicked by an authenticated admin, causes the admin's browser to submit a request that stores XSS payloads in the plugin's database. When other users view the affected pages, the stored scripts execute.
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.
-
Confirm WP Profitshare plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Profitshare' or check the /wp-content/plugins/ directory for a profitshare-related folderAffected if The plugin is installed and active
-
Identify installed plugin versionIn WordPress admin, find WP Profitshare in Plugins list and note the version number displayed under the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/[profitshare-folder]/plugin-name.php for 'Version:' tagAffected if Version cannot be determined or is unknown/old
-
Check plugin database for suspicious stored XSSAccess WordPress database (via phpMyAdmin or CLI) and query plugin tables for XSS patterns. Look for entries containing <script, <img onerror=, javascript:, or other XSS vectors in plugin-specific tables (often named like wp_profitshare_* or similar)Affected if Database contains XSS payloads in plugin-related tables that were not intentionally added by administrators
-
Inspect admin action forms for CSRF tokensNavigate to WP Profitshare plugin settings/admin pages in WordPress admin. View page source (right-click > View Page Source) and search for forms submitting to plugin admin actions. Check if each form includes a hidden input with name containing 'nonce' or '_wpnonce'Affected if Forms performing state-changing actions lack CSRF nonce fields or the nonce is not validated server-side (requires code review of plugin handler)
User is affected if WP Profitshare plugin is installed and either the version lacks CSRF protection or suspicious XSS payloads exist in the plugin's database tables.
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 CSRF token (nonce) validation for all state-changing operations in the plugin and apply proper input sanitization/output encoding to prevent stored XSS. Upgrade to the latest plugin version if available.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31906 — 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-31906 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