CVE-2025-28986
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 Webaholicson Epicwin Plugin epicwin-subscribers allows SQL Injection.This issue affects Epicwin Plugin: from n/a through <= 1.5.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in the epicwin-subscribers component of the Epicwin Plugin allows authenticated administrators to unknowingly trigger SQL injection attacks. Attackers can craft malicious web pages that, when visited by a logged-in admin, cause the browser to send forged requests to the vulnerable endpoint, enabling arbitrary SQL command execution.
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
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify if Epicwin plugin is installedCheck the WordPress plugins directory or admin panel for the Epicwin plugin presence. Common paths: /wp-content/plugins/ or via WordPress admin > Plugins.Affected if Epicwin plugin is not installed means this CVE does not apply
-
Determine the installed Epicwin plugin versionRead the main plugin file header (e.g., epicwin.php) to find the Version comment, or check the plugin metadata in WordPress admin under Plugins > Installed Plugins.Affected if Version cannot be determined or is unknown - treat as potentially affected
-
Verify the epicwin-subscribers component existsCheck for the presence of subscriber-related files in the plugin directory, such as files named 'subscribers.php', 'subscriber.php', or a 'subscribers' folder within the Epicwin plugin structure.Affected if The epicwin-subscribers component is present and active in the plugin
-
Confirm admin authentication stateDetermine if any administrator session is active or was recently active on the WordPress site, as the CSRF attack requires a logged-in administrator to trigger the forged request.Affected if An administrator user is authenticated or has an active session on the site
-
Inspect subscribers endpoint for anti-CSRF protectionExamine the code handling subscriber state-changing operations (add/edit/delete functions) in the epicwin-subscribers component for presence of nonce tokens, CSRF tokens, or referer validation. Check if form submissions or AJAX calls include anti-CSRF mechanisms.Affected if No anti-CSRF tokens or origin validation are found on state-changing operations in the subscribers functionality
A user is affected if the Epicwin plugin is installed with the epicwin-subscribers component present and the endpoint lacks anti-CSRF protections on state-changing operations, combined with an active administrator session.
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 anti-CSRF tokens and origin validation on all state-changing operations in the epicwin-subscribers functionality, and parameterize database queries to prevent the SQL injection that CSRF can trigger.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28986 — 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-28986 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