Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain admin-level WordPress account
-
DeliverySend crafted request to vulnerable plugin parameter
-
ExploitInject blind SQL payload
-
ExecutionInfer data via response/timing differences
-
ImpactExfiltrate database contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated WordPress user holding HIGH privileges (PR:H in the CVSS vector), effectively administrator-level access, to reach the vulnerable plugin functionality - it is NOT remotely exploitable by anonymous users. The 'Post title marquee scroll' plugin by Gopiplus (versions up to and including 9.9) must be installed and active on the target WordPress site. The limiting factor is the admin-level authentication prerequisite, which sharply restricts the realistic attacker population; no special non-default configuration or user interaction is required once that privilege is held. Being a blind injection, exploitation also requires iterative inference (boolean/time-based) rather than direct data return. |
| Impact | This is a blind SQL injection (CWE-89) in the Gopiplus 'Post title marquee scroll' WordPress plugin, reported by Patchstack and rated CVSS 7.6. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L indicates a network-reachable, low-complexity attack with no user interaction, but critically requires HIGH privileges (PR:H) - meaning the attacker must already be an authenticated administrator-level user before exploitation. No EPSS score is provided, the CVE is NOT on the CISA KEV list, and no public proof-of-concept is referenced, so this is 'no public exploit identified at time of analysis.' The real-world risk is materially lower than the 7.6 headline suggests: the PR:H requirement means an attacker already holding admin access is largely the only viable actor, and such an attacker can typically already read the database through legitimate means, which undercuts the blind-SQLi value. The S:C (scope changed) and A:L (low availability impact) choices in the input vector are debatable for a contained plugin SQL injection and should be treated with caution - see assessed vector below. Net: a genuine vulnerability worth patching, but a low-urgency, low-exploitation-probability issue rather than an emergency, given the obscure plugin and the admin-level precondition. |
| Exploit ScenarioDerived | An authenticated administrator (or an attacker who has already compromised an admin account via phishing or credential reuse) submits crafted input to the vulnerable plugin parameter, injecting boolean- or time-based blind SQL payloads. By observing differential responses or response timing, the attacker iteratively extracts database contents such as user records and password hashes. No public exploit code is currently known for this specific CVE. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Blind SQL injection in the Gopiplus 'Post title marquee scroll' WordPress plugin (all versions through 9.9) allows an authenticated user with administrator-level privileges to inject arbitrary SQL into backend database queries and infer data through boolean- or time-based responses. The highest realistic impact is full disclosure of data stored in the WordPress database (CVSS:C:H), with the attacker population sharply constrained by the PR:H prerequisite - anonymous visitors and ordinary subscribers cannot reach the vulnerable functionality. As of analysis there is no CISA KEV listing and no public exploit code identified, and because the injection is blind, successful exploitation requires iterative inference rather than direct retrieval of results; the vendor has not published a fixed version, so the plugin should be removed or disabled until an update appears.
RemediationAI
No vendor-released patch has been identified at time of analysis, and no fixed version number is available in the provided intelligence; the plugin's advisory of record is the Patchstack entry at https://patchstack.com/database/wordpress/plugin/post-title-marquee-scroll/vulnerability/wordpress-post-title-marquee-scroll-plugin-9-9-sql-injection-vulnerability?_s_id=cve, which should be monitored for a patched release covering versions above 9.9. Until an update ships, the most effective action is to deactivate and remove 'Post title marquee scroll' from every WordPress installation where it is not strictly required - this fully eliminates the attack surface, with the only trade-off being loss of the marquee display functionality (substitute a maintained alternative plugin if needed). If the plugin must remain active, restrict the administrator population by applying least privilege: audit wp_users and wp_usermeta for unnecessary administrator accounts, downgrade them to Editor or lower, and enforce strong authentication plus rate limiting on wp-login.php and XML-RPC, understanding that this only shrinks the pool of principals who can trigger the injection rather than removing the bug, since any remaining administrator remains a viable attacker. Site-level database hardening - least-privilege MySQL users that cannot read unrelated schemas, and WAF or plugin-level rules matching SQLi patterns in requests to the marquee plugin's endpoints - can raise the cost of exploitation but should be treated as compensating controls, not fixes, because blind time-based injection payloads are often obfuscated to evade signature detection.
Affected VersionsENISA
Affected Packages
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 flaw is a classic SQL injection (CWE-89) in a WordPress plugin, where user-supplied input is concatenated into an SQL statement without proper neutralization or use of the $wpdb->prepare() parameterization API. Patchstack's advisory describes it specifically as Blind SQL Injection, meaning the application does not reflect query results or error output back to the attacker, so exploitation proceeds by asking the database true/false questions (boolean-based) or by measuring response delays (time-based) to reconstruct schema and data one bit at a time. The affected component is identified by the CPE cpe:2.3:a:gopiplus:post_title_marquee_scroll:*:*:*:*:*:*:*:*, a wildcard covering every released version up to and including 9.9, so no configuration difference narrows the exposure - the only gating factor is the plugin being installed and active. The supplied CVSS vector (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L) differs from our independent assessment (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N): we do not treat the injection as crossing a security scope boundary, and we assess no availability impact, while both agree the vector is network-reachable, low complexity, no user interaction, and requires high (administrator) privileges with high confidentiality loss.
Know when Post Title Marquee Scroll 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
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
Admin-level access needed so PR:H; SQLi is contained within the database so S:U not S:C, with blind read impact giving C:H and no genuine integrity or availability effect.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Gopiplus Post title marquee scroll post-title-marquee-scroll allows Blind SQL Injection.This issue affects Post title marquee scroll: from n/a through 9.9.
Executive ViewAI
A blind SQL injection flaw in the Gopiplus 'Post title marquee scroll' WordPress plugin (all versions through 9.9) could allow an attacker who already holds administrator-level credentials on a WordPress site to read data stored in the underlying database. Because exploitation requires pre-existing administrative access and there is no vendor patch or identified public exploit at this time, the practical risk to the organization is concentrated on sites where admin credentials are weak, shared, or poorly governed rather than on the general public-facing attack surface. Leadership should care because the affected plugin is unmaintained by its vendor, meaning exposure will persist until the component is removed.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate and remove the plugin entirely; restrict WordPress administrator accounts to the minimum necessary and enforce multi-factor authentication; limit wp-admin access by IP allowlist or VPN; apply database account least privilege and read-only where possible; deploy WAF or virtual patching rules targeting boolean- and time-based injection patterns on the affected plugin endpoints; and enable database query and web access logging to detect blind inference attempts.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
EUVD-2026-94287
GHSA-g2x8-5jjg-c3r2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB