dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-49887

CRITICAL · 9.9 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Improper Control of Generation of Code ('Code Injection') vulnerability in WPFactory Product XML Feed Manager for WooCommerce product-xml-feeds-for-woocommerce allows Remote Code Inclusion.This issue affects Product XML Feed Manager for WooCommerce: from n/a through <= 2.9.3.

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

Code injection vulnerability in WPFactory Product XML Feed Manager for WooCommerce allows remote code inclusion, enabling attackers to inject and execute malicious code on the server through the plugin's XML feed generation functionality.

MitigationImmediately update the plugin to the latest patched version or disable/remove the plugin until a patch is available. Review server for any malicious files or unauthorized access since the CVSS score indicates active exploitation potential.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify the plugin is installed
    Check your WordPress plugins directory (wp-content/plugins) for the folder 'xml-feed-manager-for-woocommerce' or search for 'WPFactory Product XML Feed Manager' in your WordPress admin Plugins page
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed version
    In WordPress admin, go to Plugins > Installed Plugins > Product XML Feed Manager for WooCommerce and note the version number displayed, or read the main plugin file header in wp-content/plugins/xml-feed-manager-for-woocommerce/
    Affected if The version cannot be determined or is older than the patched version
  3. Check XML feed endpoint accessibility
    Look for the plugin's XML feed URL pattern (commonly /?xml_feed=1 or /feed/xml or similar) by reviewing plugin settings or checking for generated feed URLs in the WordPress site source
    Affected if XML feed generation is enabled and publicly accessible
  4. Inspect feed generation code for injection points
    Examine the plugin file handling XML feed creation (typically in includes/class-xml-feed-manager.php or similar) for unsanitized parameters passed to include/require/eval functions
    Affected if The code uses user-supplied input without proper sanitization in file inclusion or execution contexts
  5. Review server for suspicious files
    Check wp-content/uploads/ and wp-content/plugins/ directories for newly created PHP files with random names, encoded content, or files modified around the time of potential exploitation
    Affected if Unexpected PHP files exist that were not intentionally uploaded

The environment is affected if the WPFactory Product XML Feed Manager for WooCommerce plugin is installed with a version prior to the patched release AND the XML feed generation feature is accessible to unauthenticated users.

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

Immediately update the plugin to the latest patched version or disable/remove the plugin until a patch is available. Review server for any malicious files or unauthorized access since the CVSS score indicates active exploitation potential.

Recommended fix Moderate confidence

Latest version of Product XML Feed Manager for WooCommerce (version > 2.9.3)

  1. 1. Backup your WordPress site and database before performing any updates
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Locate 'Product XML Feed Manager for WooCommerce' by WPFactory
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin version is newer than 2.9.3
  6. 6. Test that product XML feed generation still functions correctly
  7. 7. Monitor the site for any unusual behavior
Caveat Minor - verify XML feed templates work correctly after upgrade as structure may have changed

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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