CVE-2025-8315
BaseFortify
Publication date: 2025-08-05
Last updated on: 2025-08-05
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | wordpress | * |
| wordfence | wp_easy_contact | * |
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?
CVE-2025-8315 is a Stored Cross-Site Scripting (XSS) vulnerability in the WP Easy Contact WordPress plugin, specifically via the 'noaccess_msg' parameter in versions up to 4.0.1. Due to insufficient input sanitization and output escaping, authenticated users with Contributor-level access or higher can inject malicious scripts into pages. These scripts execute whenever any user accesses the affected page, potentially compromising site security. [1, 2]
How can this vulnerability impact me? :
This vulnerability allows authenticated attackers with Contributor-level access or above to inject arbitrary web scripts into the site. These scripts can execute in the browsers of users who visit the injected pages, potentially leading to theft of user credentials, session hijacking, defacement, or other malicious actions. It compromises the integrity and security of the website and its users. [1, 2]
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 WP Easy Contact plugin version installed is 4.0.1 or earlier, as these versions are vulnerable to stored XSS via the 'noaccess_msg' parameter. To detect exploitation attempts, you can monitor HTTP requests for suspicious payloads in the 'noaccess_msg' parameter, especially from authenticated users with Contributor-level access or higher. For example, using command-line tools like curl or grep on web server logs to find requests containing script tags or suspicious JavaScript in the 'noaccess_msg' parameter. Example commands: 1) grep -i 'noaccess_msg=.*<script' /var/log/apache2/access.log 2) Use curl to test injection: curl -X POST -d "noaccess_msg=<script>alert(1)</script>" https://yourwordpresssite.com/wp-admin/admin.php?page=wp_easy_contact 3) Check plugin version via WP-CLI: wp plugin get wp-easy-contact --field=version [1, 2]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the WP Easy Contact plugin to version 4.0.2 or later, where the vulnerability related to the 'noaccess_msg' parameter has been fixed by proper input sanitization and output escaping. Additionally, restrict Contributor-level and higher user permissions to trusted users only, and monitor for suspicious activity related to the plugin. If updating immediately is not possible, consider disabling the plugin temporarily or applying manual sanitization patches as described in the version 4.0.2 changelog. [1, 2]