CVE-2025-30959
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 · uneditedMissing Authorization vulnerability in WPFactory Product XML Feed Manager for WooCommerce product-xml-feeds-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Product XML Feed Manager for WooCommerce: from n/a through <= 2.9.2.
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 confidenceMissing authorization vulnerability in WPFactory Product XML Feed Manager for WooCommerce plugin versions up to 2.9.2 allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to product XML feed data or administrative functions.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the plugin is installedNavigate to WordPress admin > Plugins and verify 'Product XML Feed Manager for WooCommerce' by WPFactory is listed as activeAffected if the plugin is installed and active
-
Identify the installed versionIn Plugins list, click on the plugin details or check the plugin header in /wp-content/plugins/product-xml-feed-manager-for-woocommerce/ folder for the 'Version' fieldAffected if the version number is 2.9.2 or lower (any version 'up to 2.9.2')
-
Locate XML feed endpointsCheck your site's robots.txt or sitemap for XML feed URLs (typically /xml-feed/, /feed/xml/, or custom feed paths defined in plugin settings)Affected if XML feed URLs are accessible on the site
-
Test endpoint authorizationAttempt to access the identified XML feed URLs from an unauthenticated browser session (incognito/private window) without logging into WordPressAffected if the feed loads and displays product data without requiring login or returning a 401/403 error
-
Verify admin function access controlsCheck plugin settings pages under WooCommerce > Product XML Feeds and test direct access to any admin-action URLs (e.g., ?action=xml_feed_*) while logged outAffected if admin functions or settings pages load without authentication or proper capability checks
A user is affected if the plugin is installed with version 2.9.2 or lower AND the XML feed endpoints or admin functions are accessible without authentication.
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 dataUpdate to the latest version of Product XML Feed Manager for WooCommerce once the patch is released. If no update is available, implement additional access controls at the web server or WAF level to restrict access to the affected plugin endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30959 — 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-30959 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