CVE-2026-28115
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in loopus WP Attractive Donations System - Easy Stripe & Paypal donations WP_AttractiveDonationsSystem allows Blind SQL Injection.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 · high confidenceA blind SQL injection vulnerability exists in the WP Attractive Donations System WordPress plugin. The vulnerability allows unauthenticated attackers to inject malicious SQL queries through unsanitized input parameters used in database operations, potentially allowing extraction of sensitive data from the WordPress database.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 plugin installationList the installed WordPress plugins in wp-content/plugins/ and verify that WP Attractive Donations System is presentAffected if The plugin directory wp-attractive-donations or similar exists in the plugins folder
-
Identify installed versionOpen the main plugin PHP file or readme.txt in the plugin directory and locate the version declarationAffected if The version number retrieved is within the affected range or cannot be determined (assume affected if unpatched)
-
Verify public-facing donation formsAccess the website frontend and locate any donation forms, donation submission pages, or plugin-related endpoints that accept user inputAffected if Public donation forms or user input pages are accessible without authentication
-
Inspect input handling in plugin codeSearch plugin PHP files for database query functions (wpdb->prepare, $wpdb->query, etc.) that incorporate request parameters ($_GET, $_POST, $_REQUEST) without sanitizationAffected if Database queries directly use unsanitized user-supplied input from request parameters
-
Check for exploitation indicatorsReview web server access logs and WordPress audit logs for unusual SQL syntax patterns in requests to plugin endpointsAffected if Logs contain SQL injection attempt patterns or suspicious database queries originating from plugin pages
The environment is affected if the WP Attractive Donations System plugin is installed and its donation-related input parameters handle unsanitized user input in database operations
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 plugin to the latest version immediately. If no patch is available, disable the plugin until a fix is released. As a temporary measure, restrict access to the affected endpoints at the web application firewall level.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28115 — 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-28115 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