CVE-2025-5398
BaseFortify
Publication date: 2025-06-27
Last updated on: 2025-07-07
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ninjaforms | ninja_forms | to 3.10.2.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the Ninja Forms WordPress plugin (up to version 3.10.2.1) is a Stored Cross-Site Scripting (XSS) issue. It occurs because the plugin uses a templating engine that does not properly escape user-supplied data before outputting it. This allows authenticated users with contributor-level access or higher to inject malicious scripts into pages. These scripts execute whenever any user views the affected page, potentially compromising user security.
How can this vulnerability impact me? :
This vulnerability can allow attackers with contributor-level access or above to inject arbitrary web scripts into pages. When other users access these pages, the malicious scripts execute in their browsers. This can lead to theft of user credentials, session hijacking, defacement, or other malicious actions depending on the injected script's intent. It compromises the integrity and security of the website and its users.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the Ninja Forms plugin version installed is 3.10.2.1 or earlier, as these versions are vulnerable. Additionally, monitoring for suspicious stored cross-site scripting payloads in form submissions or pages generated by Ninja Forms could help detect exploitation attempts. Specific commands are not provided in the resources, but you can check the plugin version via WordPress CLI with: `wp plugin get ninja-forms --field=version` and inspect form content for injected scripts.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Ninja Forms plugin to version 3.10.2.2 or later, as indicated by the changeset that likely addresses this vulnerability. Applying this update will fix the insufficient output escaping issue that allows stored cross-site scripting. Until the update is applied, restrict contributor-level access to trusted users only to reduce risk. [1]