dbcve.org
Wp All ImportWordPress extension · Soflyy

CVE-2015-9331

HIGH · 7.5 CVSS v3.0 Published 2019-08-20
Fix available
A fix is available. Upgrade to 3.2.4 or later.
See remediation →
84/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 wp-all-import plugin before 3.2.4 for WordPress has no prevention of unauthenticated requests to adminInit.

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 wp-all-import WordPress plugin before version 3.2.4 lacks proper access control on its adminInit hook, allowing unauthenticated attackers to trigger administrative functions by sending requests to the vulnerable endpoint.

MitigationUpdate wp-all-import plugin to version 3.2.4 or later, or implement capability checks (current_user_check) before executing adminInit actions to restrict access to authenticated administrators only.

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.2.4

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
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 > Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the wp-all-import folder
    Affected if The wp-all-import plugin folder exists in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > click the plugin name to view version details, or read the main plugin PHP file header for the Version field
    Affected if The displayed version is lower than 3.2.4 (e.g., 3.2.3, 3.2.2, etc.)
  3. Verify the adminInit hook is accessible without authentication
    Inspect the main plugin PHP file (usually wp-all-import.php or similar) for add_action('adminInit', ...) calls without capability checks like current_user_check or require_admin privileges
    Affected if The adminInit action is registered without proper capability verification before executing sensitive functions

If the wp-all-import plugin is installed with a version lower than 3.2.4 and the adminInit hook lacks capability checks, the environment is vulnerable to unauthenticated administrative function execution.

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
Upgrade available Upgrade to 3.2.4 or later
Fixed in 3.2.4
Interim mitigation

Update wp-all-import plugin to version 3.2.4 or later, or implement capability checks (current_user_check) before executing adminInit actions to restrict access to authenticated administrators only.

Fix this in Wp All Import Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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