The Smart Forms – when you need more than just a contact form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 2.6.98 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
Security readout for executives and security teams
Plain-English summary
Smart Forms through version 2.6.98 can let an already authenticated WordPress administrator store malicious browser script in affected settings. The script runs when someone visits an injected page. Exposure is limited to multisite installations and installations where unfiltered_html is disabled, substantially narrowing risk.
Executive priority
Address during the normal vulnerability-remediation cycle, prioritizing exposed multisite systems and environments with weak administrator-account controls. Escalate if suspicious administrative changes appear. The privilege requirement and limited configurations reduce urgency, but persistent browser execution can affect other users.
Technical view
CVE-2025-5055 is stored cross-site scripting caused by insufficient input sanitization and output escaping in Smart Forms administrative settings. Exploitation requires administrator-level privileges, network access, and affected configuration conditions. The CVSS 3.1 score is 4.4, with potential low confidentiality and integrity impact but no stated availability impact.
Likely exposure
Likely exposure requires Smart Forms version 2.6.98 or earlier, an authenticated administrator-level attacker, and either multisite operation or disabled unfiltered_html. Ordinary single-site installations outside those stated conditions are not identified as affected by the supplied evidence.
Exploitation context
The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation. Exploitation requires high privileges and affected configuration conditions, but successful injection persists and executes without further attacker interaction when a user accesses the injected page.
Researcher notes
The supplied record maps this issue to CWE-79 and CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N. A WordPress changeset is referenced, but the bundle does not explicitly identify a fixed release. Confirm remediation status through vendor guidance rather than assuming every version after 2.6.98 is corrected.
Mitigation direction
Identify WordPress sites running Smart Forms version 2.6.98 or earlier.
Check vendor guidance and update to a release explicitly confirmed as corrected.
Remove or disable the plugin where it is unnecessary.
Restrict administrator accounts and review them for compromise.
Temporarily limit access to affected administrative settings where operationally feasible.
Validation and detection
Confirm the installed Smart Forms version on every WordPress instance.
Determine whether each instance is multisite or has unfiltered_html disabled.
Review Smart Forms settings and affected pages for unexpected scripts or markup.
Verify the installed release against current vendor correction guidance.
Confirm administrator accounts, sessions, and recent settings changes are legitimate.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.