dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-58956

HIGH · 7.1 CVSS v3.1 Published 2025-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in loopus WP Attractive Donations System wp-attractive-donations-system-easy-stripe-paypal-donations allows Stored XSS.This issue affects WP Attractive Donations System: from n/a through < 1.29.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WP Attractive Donations System WordPress plugin allows authenticated administrators to unknowingly execute malicious requests that inject Stored XSS payloads. The lack of proper nonce/token validation on sensitive admin actions enables attackers to craft forged requests that persist malicious scripts in the database.

MitigationUpdate the WP Attractive Donations System plugin to version 1.29 or later which contains the CSRF fix. Until patched, monitor admin activity and consider disabling the plugin.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin is installed
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'WP Attractive Donations System' in the list
    Affected if Plugin is not found in the installed plugins list
  2. Identify installed version
    In the plugins list, locate the WP Attractive Donations System entry and note the version number displayed beneath the plugin name
    Affected if Version number cannot be determined or is not displayed
  3. Compare against fixed version
    Compare the installed version number to the patched version 1.29
    Affected if Installed version is below 1.29 (for example, 1.28, 1.27, etc.)
  4. Verify nonce/token validation exists (optional)
    Inspect plugin source code files in wp-content/plugins/wp-attractive-donations-system/ for admin action handlers and check if nonce verification tokens are present using functions like wp_verify_nonce or check_admin_referer
    Affected if No nonce validation is found in admin action handlers

The environment is affected if the WP Attractive Donations System plugin is installed with a version below 1.29, as this version range lacks proper CSRF protection on sensitive admin actions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WP Attractive Donations System plugin to version 1.29 or later which contains the CSRF fix. Until patched, monitor admin activity and consider disabling the plugin.

Recommended fix High confidence

Version 1.29 or later of WP Attractive Donations System

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'WP Attractive Donations System' (also known as wp-attractive-donations-system-easy-stripe-paypal-donations)
  4. 4. Check the current installed version of the plugin
  5. 5. If the installed version is lower than 1.29, navigate to Plugins > Add New
  6. 6. Search for 'WP Attractive Donations System' or 'loopus'
  7. 7. Update the plugin to version 1.29 or the latest available version
  8. 8. Verify the update completed successfully

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58956 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58956 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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