CVE-2026-6391
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 Sentence To SEO (keywords, description and tags) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the create_admin_page() function. This makes it possible for unauthenticated attackers to inject malicious web scripts and update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 confidenceThe Sentence To SEO WordPress plugin has a CSRF vulnerability in the create_admin_page() function due to missing nonce validation. This allows unauthenticated attackers to forge requests that update plugin settings, potentially injecting malicious scripts that execute when an administrator accesses the affected admin page.
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
- 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.
-
Verify Sentence To SEO plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'Sentence To SEO', or check the plugin's main PHP file (usually in wp-content/plugins/sentence-to-seo/) for the 'Version' header in the plugin comment blockAffected if The installed version is 1.0 or any version earlier than the patched release
-
Locate the create_admin_page functionOpen the main plugin PHP file and search for the function definition 'function create_admin_page()' to confirm it exists in the codebaseAffected if The function exists in the plugin code, indicating the vulnerable code path is present
-
Inspect nonce validation in create_admin_pageExamine the create_admin_page() function body for nonce verification calls (such as wp_verify_nonce, check_admin_referer, or check_ajax_referer) and admin permission checks (such as current_user_can)Affected if The function lacks nonce validation and permission checks, making it vulnerable to CSRF attacks
-
Review plugin settings for unauthorized changesNavigate to the plugin's admin settings page (usually under Settings or a dedicated menu item) and inspect all configurable options for suspicious or unexpected valuesAffected if Settings contain unexpected values, unfamiliar scripts, or malicious URLs that were not intentionally configured
You are affected if the Sentence To SEO plugin version is 1.0 or earlier AND the create_admin_page() function lacks nonce validation and permission checks, or if plugin settings show unauthorized modifications.
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 to a patched version when available; implement nonce validation and capability checks on the create_admin_page() function and all admin action handlers.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6391 — 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-6391 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