dbcve.org
Wp All ImportWordPress extension · Soflyy

CVE-2018-16259

MEDIUM · 6.1 CVSS v3.0 Published 2019-04-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
There is an XSS vulnerability in WP All Import plugin 3.4.9 for WordPress via pmxi-admin-settings large_feed_limit. NOTE: The vendor states that this is not a vulnerability. WP All Import is only able to be used by a logged in administrator, and the action described can only be taken advantage of by a logged in administrator

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

Reflected XSS vulnerability in WP All Import plugin version 3.4.9 for WordPress, specifically in the pmxi-admin-settings page via the large_feed_limit parameter. The vulnerability allows injection of malicious scripts through this input field.

MitigationApply proper input sanitization and output encoding to the large_feed_limit parameter and all settings parameters in pmxi-admin-settings. Consider upgrading to a newer plugin version if available.

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
Wp All ImportWordPress extension
Affected:= 3.4.9

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
None

CVSS:3.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP All Import plugin is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'WP All Import' in the list
    Affected if Plugin is not listed in the installed plugins
  2. Check installed plugin version
    In the Plugins page, click on the plugin name or view details to find the version number. Compare against 3.4.9
    Affected if Version displayed is exactly 3.4.9
  3. Confirm plugin is active
    On the Plugins page, verify the WP All Import plugin shows as 'Active' (not deactivated)
    Affected if Plugin is activated and accessible in the admin panel
  4. Verify access to vulnerable settings page
    Access the pmxi-admin-settings page by navigating to All Import > Settings in the WordPress admin sidebar. Check if the page loads successfully
    Affected if Settings page is accessible and the large_feed_limit parameter field exists on the page

You are affected if the WP All Import plugin version is exactly 3.4.9 AND the plugin is active with the pmxi-admin-settings page accessible, allowing the large_feed_limit input field to be manipulated.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply proper input sanitization and output encoding to the large_feed_limit parameter and all settings parameters in pmxi-admin-settings. Consider upgrading to a newer plugin version if available.

Fix this in Wp All Import Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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