CVE-2026-7467
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 · uneditedThe Read More & Accordion plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.5.7. This is due to the 'RadMoreAjax::importData' function not restricting which database tables can be written to during import and not properly validating the imported data. This makes it possible for authenticated attackers, with permission granted by the site owner through the plugin's role settings, to insert arbitrary rows into the 'wp_users' and 'wp_usermeta' tables, including the 'wp_capabilities' field, allowing them to create a new administrator account and gain administrator access to the site.
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 confidenceThe Read More & Accordion plugin for WordPress contains a privilege escalation vulnerability in the RadMoreAjax::importData function in versions up to 3.5.7. The function fails to restrict which database tables can be written to during import operations and lacks proper validation of imported data. This allows authenticated attackers with plugin-granted permissions to insert arbitrary rows into wp_users and wp_usermeta tables, including modifying the wp_capabilities field to create new administrator accounts and gain full admin access.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify plugin installation and versionLocate the plugin in wp-content/plugins/read-more-accordion/ or use WordPress CLI: wp plugin list --name='read-more-accordion' to retrieve the installed version. Compare against the affected range (versions up to 3.5.7).Affected if Plugin is installed and version is 3.5.7 or earlier
-
Check import functionality access settingsIn WordPress admin panel, navigate to the plugin settings and locate the role/permission configuration for the import feature. Identify which user roles have access to the import functionality.Affected if Import functionality is enabled for any role other than Administrator, or role settings are accessible to authenticated users
-
Audit administrator accountsList all user accounts with administrator role using wp user list --role=administrator or by querying the wp_users table directly. Verify the creation date and creator of each account.Affected if Unexpected or unauthorized administrator accounts exist, especially accounts created recently that were not created through WordPress admin registration
-
Inspect wp_capabilities in usermetaQuery the wp_usermeta table for meta_key='wp_capabilities' where meta_value contains 'administrator'. Cross-reference user IDs with legitimate admin accounts.Affected if wp_capabilities meta entries show administrator role for accounts that should not have elevated privileges
Environment is affected if the Read More & Accordion plugin version is 3.5.7 or earlier AND the import feature is accessible to non-administrator users, or if unauthorized administrator accounts exist in the database.
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.
dbcve · scopedUpdate the plugin to version 3.5.8 or later immediately. Review user accounts for unauthorized administrators and audit the plugin's role settings to restrict or disable the import functionality until the patch is applied.
Version 3.5.8 or later of the Read More & Accordion WordPress plugin
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the 'Read More & Accordion' plugin
- Check the current version number to confirm it is 3.5.7 or below
- Click 'Update Now' if an update is available, or manually download version 3.5.8 or later from the WordPress plugin repository
- Activate the updated plugin after installation
- Verify the plugin is running version 3.5.8 or later in the Plugins list
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7467 — 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-2026-7467 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