CVE-2025-8318
BaseFortify
Publication date: 2025-09-11
Last updated on: 2025-09-11
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ben_marshall | jobify | 1.4.4 |
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?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the Jobify WordPress plugin, specifically via the 'keyword' parameter. It occurs because the plugin does not properly sanitize or escape input, allowing authenticated users with Contributor-level access or higher to inject malicious scripts. These scripts are then stored and executed whenever any user views the affected page, potentially compromising user security.
How can this vulnerability impact me? :
The vulnerability can allow attackers with Contributor-level access to inject malicious scripts into pages viewed by other users. This can lead to unauthorized actions such as stealing user credentials, session hijacking, defacement, or spreading malware. Since the scripts execute in the context of the affected site, it can compromise the security and trustworthiness of the website for all users.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying if the Jobify WordPress plugin version 1.4.4 or earlier is installed and active on your system. Since the vulnerability involves stored Cross-Site Scripting via the 'keyword' parameter, you can test for it by submitting crafted input containing script tags in the 'keyword' parameter on pages where the plugin processes job search queries. For detection on the system, you can check the plugin version with the following WP-CLI command: `wp plugin list --status=active | grep jobify`. Additionally, monitoring HTTP requests for suspicious payloads in the 'keyword' parameter or scanning stored pages for injected scripts can help detect exploitation. No specific detection commands are provided in the resources. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or deactivating the Jobify plugin if it is installed and active, especially since the plugin has been temporarily removed from download availability pending a security review. Restrict Contributor-level and above user permissions to trusted users only, as the vulnerability requires authenticated access at that level. Monitor and sanitize inputs related to the 'keyword' parameter manually if possible. Await and apply any official security patches or updates once available. Since no patch or update is currently available, removing or disabling the plugin is the safest immediate action. [1]