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

CVE-2025-26568

HIGH · 7.1 CVSS v3.1 Published 2025-02-13
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 jensmueller Easy Amazon Product Information easy-amazon-product-information allows Stored XSS.This issue affects Easy Amazon Product Information: from n/a through <= 4.0.1.

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

A CSRF vulnerability in the Easy Amazon Product Information WordPress plugin (versions <= 4.0.1) allows attackers to craft malicious requests that, when triggered by an authenticated administrator, result in Stored XSS. The attacker tricks the admin into submitting a crafted form that injects malicious scripts into the database.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing forms and validate these tokens on submission. Additionally, properly sanitize and escape all user-supplied and stored data before output to prevent the stored XSS.

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 Easy Amazon Product Information plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Easy Amazon Product Information' in the plugin list.
    Affected if The plugin is not found in the installed plugins list, then the site is not affected by this vulnerability.
  2. Determine the installed version of the plugin
    In the Plugins list, find 'Easy Amazon Product Information' and note the version number displayed below the plugin name.
    Affected if The installed version is 4.0.1 or lower, indicating the plugin is within the vulnerable version range.
  3. Inspect plugin forms for anti-CSRF token presence
    Use browser developer tools or manually examine the plugin's PHP source files (typically in wp-content/plugins/easy-amazon-product-information/). Look at all HTML forms generated by the plugin and check if each form includes a wp_nonce_field() or similar nonce verification mechanism.
    Affected if Forms that handle state-changing operations (such as saving settings, adding/editing products) lack nonce tokens, meaning the plugin is vulnerable to CSRF attacks.
  4. Verify data sanitization on form submissions
    Review the plugin's PHP code that handles form submissions. Check if input data is processed through sanitization functions (such as sanitize_text_field(), esc_attr(), or similar) before being saved to the database.
    Affected if Form submission handlers do not properly sanitize user inputs before storing them, allowing malicious script content to be saved.
  5. Check output escaping for stored data
    Examine the plugin code that displays stored data in the admin dashboard or on the frontend. Verify that all user-supplied data retrieved from the database is passed through escaping functions (such as esc_html(), esc_attr(), or wp_kses()) before output.
    Affected if Stored data is output without proper escaping, which would allow the injected XSS payload to execute when the data is displayed.

A site is affected if the Easy Amazon Product Information plugin version is 4.0.1 or lower and the plugin's forms lack CSRF nonce protection, allowing Stored XSS to be injected via a crafted request.

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

Implement anti-CSRF tokens (nonces) on all state-changing forms and validate these tokens on submission. Additionally, properly sanitize and escape all user-supplied and stored data before output to prevent the stored XSS.

Recommended fix Moderate confidence

Any version newer than 4.0.1 (check WordPress plugin repository for latest release)

  1. Check if the WordPress site uses the 'Easy Amazon Product Information' plugin by jensmueller
  2. Navigate to WordPress admin dashboard > Plugins section
  3. Locate the Easy Amazon Product Information plugin
  4. Verify the current installed version is <= 4.0.1
  5. Check for an available plugin update to a version newer than 4.0.1
  6. If an update is available, update the plugin to the latest version
  7. If no update is available from the WordPress plugin repository, contact the plugin developer for a patched release

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