Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as WordPress administrator
-
DeliveryStore encoded template-injection payload in popup text block
-
ExploitFilter strips delimiters before decode reconstructs them
-
ExecutionTemplate engine evaluates expression server-side
-
ImpactRead PHP constants (DB credentials, auth keys)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V1 - Encoding and Sanitization Template injection prevention
|
| Exploitation Conditions | Requires an authenticated WordPress administrator account on a site running Smart Popup by Supsystic before version 2.0.2 (PR:H). The attacker must be able to create or edit a popup and insert a template-injection payload into a popup text block; successful evaluation depends on the plugin's ordering flaw where the delimiter-stripping filter runs before the decoding step that reconstructs the template delimiters, so a plainly-delimited payload would be stripped - the payload must be encoded such that decoding re-forms the delimiters after filtering. The primary limiting factor is the administrator privilege requirement, which confines exploitation to trusted/insider admins or a hijacked admin session rather than unauthenticated remote attackers; no victim user interaction is required (UI:N). |
| Impact | This is a high-CVSS-component but moderate-real-risk issue. The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N → 4.9) is internally consistent with the description: the attack is over the network against the WordPress admin interface (AV:N), is low-complexity (AC:L), requires no victim interaction (UI:N), and the PR:H reflects that only an authenticated administrator can reach the vulnerable popup text block. Impact is confidentiality-only (C:H, I:N, A:N), matching the described outcome of reading PHP constants such as database credentials and authentication keys via server-side template evaluation. The dominant mitigating signal is PR:H: an attacker must already hold administrator access, which sharply narrows the realistic threat to insider/least-privilege-escalation scenarios or a compromised admin account rather than opportunistic external attack. There is no EPSS score, no KEV listing, and no SSVC exploitation data in the input, so widespread-exploitation probability cannot be quantified from this data. A PoC reference exists (WPScan) but is not verified as working exploit code, and the vuln.today decision label is 'this_month' - a scheduled-remediation priority, not an emergency. Net: patch within the normal cycle; the admin-only barrier keeps this well below drop-everything urgency, but the ability to exfiltrate DB credentials and auth keys makes it meaningful where admin accounts are not fully trusted. |
| Exploit ScenarioDerived | An authenticated administrator (or an attacker who has compromised an admin account) stores a template-injection payload inside a Smart Popup text block; because the delimiter-stripping filter runs before the decoding step that reconstructs the delimiters, the payload survives into the template engine and is evaluated server-side. The attacker uses this to read PHP constants and exfiltrate the site's database credentials and authentication keys. A public PoC reference exists (WPScan) but it is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Authenticated attackers holding a WordPress administrator account can store an encoded template-injection payload in a Smart Popup by Supsystic text block, which the plugin's template engine later evaluates server-side, allowing PHP constants such as database credentials and authentication keys to be read. Only sites running the plugin before version 2.0.2 are affected. Exploitation requires high privileges (PR:H) with no victim interaction, which confines realistic exposure to trusted or insider administrators or a hijacked admin session; the vulnerability is not in CISA KEV, and the available WPScan reference is a public PoC reference that is not verified as working exploit code. The vendor has released a fix, and the priority label is this_month.
RemediationAI
Update Smart Popup by Supsystic to version 2.0.2 or later; the vendor patch is available, and 2.0.2 is the fixed release indicated by the affected-version data, with details in the WPScan advisory at https://wpscan.com/vulnerability/cf475664-aa8f-49ec-b1d6-62139dbad8d4/. Because the prerequisite is an administrator-level account able to create or edit popups, limiting administrator and popup-editing access to trusted accounts reduces exposure but does not remove the flaw for those users, and only the vendor update fully closes the template-evaluation path. Where updating cannot be performed immediately, deactivating or removing the plugin stops the vulnerable template engine from processing stored popup content, at the cost of losing the popup functionality; stored popup content should be reviewed for unexpected encoded template syntax before the plugin is re-enabled. No other vendor-stated workaround is provided in the available data.
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 server-side template injection in the popup rendering path of the Smart Popup by Supsystic WordPress plugin. The plugin attempts to neutralise template delimiters in popup text-block content with a filter, but that filter executes before a decoding step that can reconstruct the delimiters, so an attacker who encodes the payload can pass it through filtering and have it re-formed into live template syntax at evaluation time. The template engine then evaluates arbitrary expressions server-side, and the disclosed impact is read-only leakage of PHP constants, including database credentials and authentication keys, consistent with the assessed C:H/I:N/A:N vector. No CWE identifier was supplied with the source data, so the root-cause class is characterised here from the description as an input-filtering ordering error rather than mapped to a formal weakness ID. The supplied CPE (cpe:2.3:a:unknown:smart_popup_by_supsystic) records the vendor field as unknown, so product identification rests on the plugin name and the EUVD affected-version range of 0 to <2.0.2 rather than a confirmed vendor CPE binding. The precise template syntax and the exact decoding routine are not described in the available sources, and the trigger for evaluation beyond editing a popup text block is likewise not detailed.
Know when Smart Popup By Supsystic 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:U/C:H/I:N/A:N
Network-reachable admin UI (AV:N/AC:L), administrator required so PR:H, no interaction (UI:N); impact is confidentiality-only (C:H) reading DB credentials, with no integrity or availability effect described.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
2DescriptionCVE.org
The Smart Popup by Supsystic WordPress plugin before 2.0.2 does not prevent template-injection payloads from being stored in a popup text block and later evaluated by its template engine, because the filter meant to strip template delimiters runs before a decoding step that reconstructs them, allowing an authenticated administrator to execute arbitrary template expressions server-side and read PHP constants such as the site's database credentials and authentication keys.
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
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
More in Smart Popup By Supsystic
View allPrivilege escalation in the Smart Popup by Supsystic WordPress plugin (all versions through 1.12.0) enables unauthentica
SQL injection in the 'sidx' parameter of the Smart Popup by Supsystic WordPress plugin (all versions up to and including
EUVD-2026-111973
GHSA-mpjc-mm6h-74q4
NVD
CVE.org
Vulnrichment
Exploit-DB