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

CVE-2025-31904

HIGH · 7.1 CVSS v3.1 Published 2025-04-01
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 Infoway LLC Ebook Downloader ebook-downloader allows Cross Site Request Forgery.This issue affects Ebook Downloader: from n/a through <= 1.0.

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

CSRF vulnerability in Infoway LLC Ebook Downloader plugin allows remote attackers to trick authenticated users into performing unwanted actions (like unauthorized downloads or account changes) by forging HTTP requests due to missing or inadequate anti-CSRF token validation.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and validate tokens server-side; also add SameSite cookie attributes and Origin/Referer header checks as defense-in-depth.

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. Identify if Infoway LLC Ebook Downloader plugin is installed
    Access your CMS admin panel (such as WordPress, Drupal, or Joomla depending on the platform) and navigate to the plugins section. Look for 'Ebook Downloader' by Infoway LLC in the list of installed plugins. Alternatively, search the filesystem for plugin files named 'ebook-downloader' or containing 'infoway' in the plugin directory.
    Affected if The plugin is present in the plugins directory and shows as installed or active in the CMS
  2. Determine the installed plugin version
    In the CMS admin panel, click on the Ebook Downloader plugin to view its details page, which typically displays the version number. Alternatively, inspect the plugin's main PHP file (usually in wp-content/plugins/ebook-downloader/ or similar path) and look for a version constant or header comment stating 'Version: x.x.x'.
    Affected if The plugin version cannot be verified or differs from a patched release (no specific version range provided, so any version is potentially affected)
  3. Inspect plugin forms for CSRF token presence
    Navigate to any form provided by the Ebook Downloader plugin (such as download request forms, user settings forms, or admin configuration pages). View the page source (right-click > View Page Source) and search for input fields named 'csrf_token', '_token', 'nonce', 'wpnonce', or similar anti-CSRF token identifiers within the <form> tags.
    Affected if Forms lack any hidden token field with a random value, or the token field exists but is not validated server-side (requires code inspection)
  4. Check for SameSite cookie attributes and Origin/Referer validation
    Use browser developer tools (F12 > Network tab) to capture a request when interacting with the plugin. Inspect the request headers for 'Origin' or 'Referer' fields being checked. Alternatively, if you have access to the plugin source code, search for 'SameSite', 'Origin', 'HTTP_ORIGIN', '$_SERVER[HTTP_REFERER]', or 'validate' functions that verify these headers.
    Affected if No SameSite cookie attributes are set and no Origin/Referer header validation is performed on state-changing requests
  5. Verify state-changing operations lack server-side token validation
    If you have access to the plugin source code, examine PHP files handling form submissions (typically in files with names like 'submit', 'download', 'save', 'update', 'process', or 'handler'). Search for functions that verify nonce or token values, such as 'wp_verify_nonce', 'check_admin_referer', 'verify_nonce', or custom validation routines. Check if these validation calls are present before processing any POST/GET requests that modify data.
    Affected if No server-side token verification code is found before executing state-changing operations like downloads, settings changes, or user modifications

Your environment is affected if the Infoway LLC Ebook Downloader plugin is installed and active, and any of the following are true: the plugin version is unverified, forms lack CSRF tokens, or the server-side code does not validate anti-CSRF tokens on state-changing operations.

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

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and validate tokens server-side; also add SameSite cookie attributes and Origin/Referer header checks as defense-in-depth.

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-31904 — 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-31904 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