dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-22715

HIGH · 7.5 CVSS v3.1 Published 2026-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Missing Authorization vulnerability in loopus WP Attractive Donations System - Easy Stripe & Paypal donations WP_AttractiveDonationsSystem allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Attractive Donations System - Easy Stripe & Paypal donations: from n/a through <= 1.25.

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

The WP Attractive Donations System plugin for WordPress has a missing authorization vulnerability where the plugin fails to properly enforce access control checks on certain functionality. This allows unauthenticated or low-privileged users to access sensitive donation-related operations that should require higher privilege levels, such as administrative or donation management functions.

MitigationUpgrade to a patched version of the plugin (if available) that includes proper authorization checks. If no patched version exists, implement custom authorization middleware at the application layer to validate user capabilities before allowing access to donation system functions.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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. Verify the plugin is installed
    Navigate to WordPress admin dashboard > Plugins and confirm 'WP Attractive Donations System' is listed as an active plugin
    Affected if the plugin appears in the list of installed plugins and is activated
  2. Identify the installed version
    In the Plugins list, locate the WP Attractive Donations System entry and read the version number displayed beneath the plugin name. Alternatively, inspect the plugin main file (typically /wp-content/plugins/wp-attractive-donations-system/ or similar path containing 'attractive-donations') and look for a version constant or header
    Affected if the installed version is older than the patched version or if no patched version is publicly documented
  3. Test unauthenticated access to donation endpoints
    Using a tool like curl or Burp Suite, send GET or POST requests to common donation-related WordPress AJAX endpoints (wp-admin/admin-ajax.php?action=...) and REST API routes (/wp-json/...) associated with the donation system without providing authentication cookies or credentials
    Affected if the requests return successful responses containing donation data, donor information, or administrative functions instead of returning 401/403 errors
  4. Inspect plugin capability checks
    Access the plugin directory via FTP or file manager, locate files handling donation operations (look for functions containing 'donation', 'add', 'delete', 'update', 'manage'), and examine whether they include WordPress capability checks such as 'current_user_can()' before executing sensitive operations
    Affected if the plugin code lacks capability checks or uses weak checks that allow subscriber-level or unauthenticated access to donation management functions
  5. Verify role-based access enforcement
    Create a test user with the lowest privilege level (subscriber or contributor), log in as that user, and attempt to access or modify donation settings, view donor lists, or process donation operations through the plugin interface
    Affected if the low-privileged user can successfully perform actions that should require administrator or donation manager capabilities

If the WP Attractive Donations System plugin is installed and its version lacks documented authorization patches, or if unauthenticated/low-privileged users can access donation management functions, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of the plugin (if available) that includes proper authorization checks. If no patched version exists, implement custom authorization middleware at the application layer to validate user capabilities before allowing access to donation system functions.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22715 — 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-22715 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