Skip to main content

Praison AI SEO EUVDEUVD-2026-47884

| CVE-2026-12082 HIGH
Missing Authorization (CWE-862)
2026-07-23 WPScan GHSA-mr6p-pxvc-7864
7.5
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Discover WordPress site running Praison AI SEO
  2. Delivery
    Send unauthenticated REST API request
  3. Exploit
    Bypass missing authorization check
  4. Execution
    Read plugin configuration data
  5. Persist
    Rewrite permalink of published post
  6. Impact
    Degrade SEO and expose secrets

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires only that a WordPress site runs the Praison AI SEO plugin at a version below 5.0.7 with its REST API reachable over the network - the default state for an installed plugin, since WordPress exposes /wp-json/ routes by design. No authentication, credentials, or user interaction are needed (PR:N/UI:N confirmed by CVSS). What limits exploitation is deployment scale rather than technical prerequisites: the plugin is niche, so the population of vulnerable sites is small, and impact is bounded to reading plugin configuration data and changing post permalinks - not full site takeover. Sites that block anonymous access to /wp-json/ via a WAF or auth layer are not exploitable through this path.

Impact

Signals are mixed and should temper the 7.5 CVSS. The vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N describes trivial remote, unauthenticated, low-complexity access with high confidentiality impact and no integrity impact - yet the description explicitly says attackers can MODIFY permalinks, which is an integrity effect the vector does not capture (I:N appears understated; verify with vendor/WPScan). EPSS is low (0.19%, 8th percentile) and there is no CISA KEV listing, indicating no evidence of widespread automated exploitation despite publicly available exploit code from WPScan. The realistic priority is moderate: exploitation is easy and unauthenticated, but the affected plugin appears niche, limiting mass-exploitation appeal. Config-data disclosure is the more serious impact if the plugin stores AI-provider API keys or secrets; the permalink change is more of a nuisance/SEO-integrity issue. Treat as an important patch-soon item on affected sites rather than an emergency, absent evidence of active exploitation.

Exploit ScenarioDerived

An attacker sends anonymous HTTP requests directly to the plugin's unprotected REST API routes, reading back the plugin's configuration data (potentially including stored keys or SEO settings) and issuing a follow-up request to rewrite the permalink of a targeted published post. This requires no authentication, no user interaction, and only low attack complexity; public exploit code from WPScan lowers the bar further.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 23, 2026

Broken access control in the Praison AI SEO WordPress plugin before 5.0.7 lets unauthenticated attackers reach several REST API routes that lack authorization checks, allowing them to alter the permalink of any published post and to read the plugin's stored configuration data. WPScan reported the issue and publicly available exploit code exists, though EPSS remains low at 0.19% and it is not on CISA KEV. Exposure of configuration data (potentially including AI-service API keys and SEO settings) plus silent permalink tampering can break site links and SEO ranking with no login required.

RemediationAI

Vendor-released patch: 5.0.7 - update the Praison AI SEO plugin to version 5.0.7 or later, which is the primary and complete fix. Consult the WPScan advisory (https://wpscan.com/vulnerability/d23cb7bd-b40c-4f87-a134-7c3b62043f18/) and NVD (https://nvd.nist.gov/vuln/detail/CVE-2026-12082) for details. If immediate patching is not possible, restrict access to the plugin's REST API routes at the web server or WAF layer (for example, block or authenticate unauthenticated requests to the plugin's /wp-json/ endpoints), or deactivate the plugin entirely until it can be updated - deactivation removes all SEO functionality the plugin provides and is the safest interim step. Because configuration data may be exposed, rotate any API keys or secrets stored in the plugin's settings after upgrading, since a pre-patch read may already have leaked them.

Affected VersionsENISA

Praison AI SEO 0 <5.0.7

Affected Packages

euvd praison_ai_seo fix: 5.0.7

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is a WordPress plugin (Praison AI SEO) built on the WordPress REST API, which registers custom routes under /wp-json/. The root cause is CWE-862 (Missing Authorization): the plugin registers REST routes without a proper permission_callback (or with one that returns true), so WordPress never verifies the caller's capability before executing the handler. As a result, endpoints intended for privileged SEO management are reachable by anonymous requests. The affected CPE is cpe:2.3:a:unknown:praison_ai_seo covering all versions prior to 5.0.7. Because the flaw is at the authorization layer rather than in input parsing, no memory-safety or injection primitive is required - the attacker simply calls the exposed route directly.

Know when Praison Ai Seo gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 8.2 HIGH

Unauthenticated network REST access (AV:N/AC:L/PR:N/UI:N); config disclosure that may include secrets justifies C:H, and permalink tampering is a limited integrity impact (I:L), no availability effect.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

4
CVSS changed
Jul 23, 2026 - 15:22 NVD
7.5 (HIGH)
Patch available
Jul 23, 2026 - 10:02 EUVD
CVE Published
Jul 23, 2026 - 06:00 cve.org
HIGH 7.5
CVE Published
Jul 23, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The Praison AI SEO WordPress plugin before 5.0.7 does not perform authorization checks on several of its REST API routes, allowing unauthenticated users to modify the permalink of any published post and to read Praison AI SEO WordPress plugin before 5.0.7 configuration data.

Executive ViewAI

Why It Matters

Praison AI SEO WordPress plugin versions before 5.0.7 contain broken access control allowing unauthenticated attackers to access protected REST API routes. Threat actors can read plugin configuration (including AI service API keys) and alter post permalinks without authentication, creating dual impact: credential compromise and silent SEO ranking damage affecting any organization running this plugin.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Low
niche AI SEO WordPress plugin, small install base
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

58
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy