dbcve.org
Amazon Products To WoocommerceWordPress extension · Suhailahmad64

CVE-2025-5817

HIGH · 7.2 CVSS v3.1 Published 2025-07-02
Fix available
A fix is available. Upgrade to after 1.2.7 or later.
See remediation →
81/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
The Amazon Products to WooCommerce plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.2.7 via the wcta2w_get_urls(). This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 confidence

The Amazon Products to WooCommerce WordPress plugin (versions up to 1.2.7) contains an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in the wcta2w_get_urls() function. Attackers can leverage this to make arbitrary HTTP requests from the server, potentially accessing internal services, APIs, or infrastructure.

MitigationUpdate the plugin to version 1.2.8 or later which contains the fix. If an update is unavailable, consider disabling or removing the plugin until a patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Amazon Products To WoocommerceWordPress extension
Affected:<= 1.2.7

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
Low
Integrity
Low
Availability
None

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

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. Confirm plugin installation
    Navigate to WordPress admin > Plugins and look for 'Amazon Products to WooCommerce' or 'Suhailahmad64 Amazon Products To Woocommerce', or inspect the /wp-content/plugins/ directory for a folder matching this plugin.
    Affected if The plugin appears in the installed plugins list or directory.
  2. Check installed version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed for this plugin, or open the main plugin PHP file and look for the Version header in the plugin comment block.
    Affected if The installed version is 1.2.7 or lower.
  3. Verify vulnerable function exists
    Access the plugin files via FTP or file manager, locate the main plugin file (or files containing wcta2w_get_urls), and confirm the function is present in the code.
    Affected if The function wcta2w_get_urls() exists in the plugin code.
  4. Confirm endpoint is accessible without authentication
    Check if the wcta2w_get_urls function can be called directly via an AJAX endpoint or directly accessed URL without requiring WordPress login/authentication. Review the plugin code for add_action calls or hooks that expose this function to unauthenticated users.
    Affected if The vulnerable function is hooked to an action accessible to unauthenticated users (e.g., wp_ajax_nopriv or wp_ajax hooks without authentication checks).

If the plugin is installed, the version is 1.2.7 or lower, and the wcta2w_get_urls function is exposed to unauthenticated users, the environment is affected by CVE-2025-5817.

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
Upgrade available Upgrade to a release after 1.2.7
Interim mitigation

Update the plugin to version 1.2.8 or later which contains the fix. If an update is unavailable, consider disabling or removing the plugin until a patch is released.

Recommended fix Moderate confidence

Plugin version 1.2.8 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Amazon Products To WooCommerce' plugin
  4. Check if an update is available and update to the latest version
  5. If no update appears, manually download the latest version from wordpress.org/plugins and upload via Plugins > Add New > Upload Plugin
  6. Verify the updated version is at least 1.2.8 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Amazon Products To Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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