CVE-2025-31870
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 EXEIdeas International WP AutoKeyword wp-autokeyword allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP AutoKeyword: from n/a through <= 1.0.
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 confidenceWP AutoKeyword plugin by EXEIdeas International has a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. The vulnerability exists in the wp-autokeyword component and affects all versions up to and including 1.0, potentially allowing unauthorized access to 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify if WP AutoKeyword plugin is installedInspect the WordPress plugins directory or check the plugin list via WordPress admin panel for 'WP AutoKeyword' or 'wp-autokeyword'Affected if The plugin appears in the installed plugins list
-
Determine the installed version of WP AutoKeywordView the plugin header information via WordPress admin (Plugins > Installed Plugins > WP AutoKeyword) or inspect the main plugin file for the 'Version' comment fieldAffected if The version is 1.0 or below (since all versions up to and including 1.0 are affected)
-
Verify if the wp-autokeyword component is active and accessibleCheck if the /wp-content/plugins/wp-autokeyword/ directory exists and contains functional files; attempt to identify any publicly accessible AJAX handlers or admin-ajax.php endpoints used by the pluginAffected if The component is active and exposes unauthenticated endpoints
-
Test for missing authorization on plugin administrative functionsAttempt to access plugin settings or administrative actions without authentication (e.g., direct requests to plugin PHP files that should require admin privileges)Affected if Requests succeed without proper authentication or authorization checks
If WP AutoKeyword plugin version 1.0 or below is installed, the component is active, and administrative functions can be accessed without proper authorization, the environment is affected by CVE-2025-31870.
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 WP AutoKeyword to the latest patched version if available, or remove the plugin entirely until a security patch is released. Verify that all administrative actions in the plugin require proper authentication and authorization checks.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-31870 — 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-31870 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