Import Export For WoocommerceWordPress extension · Sidngr
CVE-2025-48144
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in sidngr Import Export For WooCommerce import-export-for-woocommerce allows Stored XSS.This issue affects Import Export For WooCommerce: from n/a through <= 1.6.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 · high confidenceA CSRF vulnerability in the Import Export For WooCommerce plugin allows attackers to inject malicious scripts through imported data. An authenticated admin can be tricked into submitting a crafted import request that stores XSS payloads in the database, which then execute when viewed by other users.
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
Import Export For WoocommerceWordPress extension
<= 1.6.2CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the plugin installation directoryCheck your WordPress plugins folder (wp-content/plugins/) for a directory named 'sidngr-import-export-for-woocommerce' or similar naming pattern containing 'import' and 'export' for WooCommerceAffected if The plugin directory does not exist - you are not affected
-
Identify the installed versionOpen the main plugin PHP file (usually named sidngr-import-export-for-woocommerce.php or similar) and locate the 'Version' field in the plugin header comment at the top of the fileAffected if The version listed is 1.6.2 or lower, or no version is declared in the header
-
Verify admin authentication statusCheck if your WordPress installation has administrator-level users with access to the WordPress admin dashboardAffected if Authenticated administrators exist - the attack requires tricking an admin to submit a crafted import request
-
Confirm import feature accessibilityLog into WordPress admin and navigate to WooCommerce > Import Export (or the plugin's menu item) to verify the import functionality is present and accessibleAffected if The import functionality exists and is accessible to admin users - this is the attack surface for the CSRF vulnerability
You are affected if the Sidngr Import Export For WooCommerce plugin is installed with version 1.6.2 or lower and the import feature is accessible to authenticated administrators.
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 dataAdd CSRF token validation to all form submissions and AJAX endpoints, and implement proper sanitization/escaping of all imported data before storage and output.
Fix this in Import Export For Woocommerce
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48144 — 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-48144 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