Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WP site with Mobile Builder + WCFM Delivery
-
ExploitSend crafted request with SQL payload in parameter
-
ExecutionInjected query executes against database
-
ImpactExfiltrate sensitive data from database
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 the target WordPress site to run BOTH the Mobile Builder plugin (version ≤1.4.2) AND the WCFM Delivery add-on simultaneously - the SQL injection is only reachable through this specific plugin combination, which is the primary limiting factor (and the basis for AC:H). No authentication is required (PR:N) and no user interaction is needed (UI:N), so against a qualifying site the attack is remote and unauthenticated. The absence of the WCFM Delivery add-on fully prevents exploitation, so the effective attack surface is restricted to the subset of Mobile Builder installations that also deploy that add-on. Impact is limited to data disclosure (C:H, I:N, A:N). |
| Impact | This is a genuine but secondary-priority issue, not a top-urgency flaw. The signals are internally consistent and point to LOW real-world risk despite a MEDIUM CVSS of 6.8: EPSS is 0.19% (8th percentile), CISA SSVC rates Exploitation as 'none' and Automatable as 'no', and the vulnerability is NOT in CISA KEV. The one elevating signal is that public exploit code exists (WPScan), but POC availability is distinct from active exploitation and the SSVC/EPSS data indicate it is not being broadly weaponized. The CVSS vector itself tempers the score: AC:H reflects that exploitation is conditional - per the description it only works on sites that ALSO run the WCFM Delivery add-on, which is a meaningful real-world constraint. PR:N confirms unauthenticated access, and C:H/I:N/A:N means impact is confidentiality-only (data disclosure via SQL injection), with no integrity or availability impact. One divergence to verify: the input scores Scope as Changed (S:C), which inflates the score, whereas typical WordPress SQLi confined to the site database is commonly scored S:U - the input score may be slightly overstated. Net: patch in normal cycle; prioritize only if the WCFM Delivery add-on is confirmed installed. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a crafted request with a malicious SQL payload in the unsanitized parameter to a WordPress site running both Mobile Builder (≤1.4.2) and the WCFM Delivery add-on, injecting SQL into a backend query to extract sensitive data such as user credentials or PII. Public exploit code is available from WPScan, lowering the barrier to attempt it, though the attack only succeeds when the WCFM Delivery add-on is present (AC:H). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
SQL injection in the Mobile Builder WordPress plugin (versions through 1.4.2) lets unauthenticated remote attackers read data from the site database, but only on installations that also run the WCFM Delivery add-on, because the vulnerable code path is reachable solely through that plugin combination. Publicly available exploit code exists (reported by WPScan) and no authentication or user interaction is required against a qualifying site; however, the dual-plugin prerequisite sharply limits the attack surface, EPSS is low at 0.19% (8th percentile), and CISA's SSVC framework rates exploitation as none with no automatable path, making this a genuine but secondary-priority issue rather than a top-urgency flaw. Impact is limited to confidentiality (C:H) with no integrity or availability effect.
RemediationAI
No vendor-released patch identified at time of analysis; monitor the WPScan advisory (https://wpscan.com/vulnerability/3f3df5b4-bcb0-4d18-bd5d-88ce5582cd47/) and the NVD entry (https://nvd.nist.gov/vuln/detail/CVE-2026-103696) for an updated release. The most effective compensating control is to deactivate or remove the WCFM Delivery add-on if it is not essential, which removes the vulnerable code path entirely at the cost of losing that add-on's functionality. If the add-on is required, deactivating the Mobile Builder plugin (or confining it to a staging environment) eliminates exposure but sacrifices the mobile builder feature. Where both must remain active, deploy WAF rules that inspect requests for SQL metacharacters targeting these plugins, accepting the trade-off that encoded or obfuscated payloads can bypass signature-based rules and that legitimate traffic may be impacted. Additionally, review database and web server logs for anomalous SQL error patterns or unexpected query activity, since exploitation attempts would likely generate errors from malformed injected statements.
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 root cause is CWE-89 (SQL Injection): a parameter in the Mobile Builder plugin is concatenated into a SQL statement without sanitization or escaping, allowing arbitrary SQL injection. The flaw is only exposed when the WCFM Delivery add-on is also active, which changes the execution path and is the reason the authoritative independent assessment rates attack complexity as High despite the network-accessible (AV:N), unauthenticated (PR:N), no-user-interaction (UI:N) vector. The supplied CVSS score of 6.8 uses S:C (scope changed) whereas the independent assessment uses S:U; both agree that impact is limited to confidentiality (C:H) with no integrity or availability effect (I:N/A:N). The CPE cpe:2.3:a:unknown:mobile_builder:*:*:*:*:*:*:*:* confirms Mobile Builder as the affected component and does not pin a vendor, consistent with the plugin being distributed via WordPress.org. SSVC scores of Exploitation:none and Automatable:no align with the fact that the vulnerability is only exploitable in a specific plugin combination.
Know when Mobile Builder 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:H/PR:N/UI:N/S:C/C:H/I:N/A:N
AV:N and PR:N for remote unauthenticated SQLi; AC:H because the WCFM Delivery add-on must also be installed; C:H data disclosure only; S:U as injection is confined to the site's own database.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The Mobile builder WordPress plugin through 1.4.2 does not sanitise and escape a parameter before using it in a SQL statement, allowing unauthenticated users to perform SQL injection attacks on sites that also run the WCFM Delivery add-on.
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.
More in Mobile Builder
View allPrivilege escalation in the Mobile Builder WordPress plugin (versions through 1.4.2) allows any authenticated low-privil
Unauthenticated SQL injection in the Mobile builder WordPress plugin (all versions through 1.4.2) lets any remote attack
EUVD-2026-102687
GHSA-p558-jrgr-752x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB