Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-7781: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in WP JobHunt

0
Medium
VulnerabilityCVE-2025-7781cvecve-2025-7781cwe-79
Published: Fri Oct 10 2025 (10/10/2025, 11:17:07 UTC)
Source: CVE Database V5
Product: WP JobHunt

Description

The WP JobHunt plugin for WordPress, used by the JobCareer theme, is vulnerable to Stored Cross-Site Scripting via the ‘cs_job_title’ parameter in all versions up to, and including, 7.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Candidate-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 16:36:12 UTC

Technical Analysis

CVE-2025-7781 is a stored cross-site scripting vulnerability identified in the WP JobHunt plugin for WordPress, which is commonly used alongside the JobCareer theme. The vulnerability exists due to improper neutralization of input during web page generation, specifically in the 'cs_job_title' parameter. This parameter is insufficiently sanitized and escaped before being rendered, allowing an authenticated attacker with at least Candidate-level access to inject arbitrary JavaScript code into pages. Because the injected scripts are stored persistently, they execute whenever any user accesses the affected page, potentially compromising user sessions, stealing credentials, or performing unauthorized actions on behalf of users. The vulnerability affects all plugin versions up to and including 7.6. The CVSS 3.1 score of 6.4 reflects a medium severity with a network attack vector, low attack complexity, privileges required, no user interaction, and a scope change indicating that the vulnerability can affect resources beyond the initially compromised component. No public exploits have been reported yet, but the presence of this vulnerability in a widely used WordPress plugin makes it a significant concern for website administrators. The lack of official patches at the time of disclosure necessitates immediate mitigation efforts to reduce risk.

Potential Impact

The impact of CVE-2025-7781 is primarily on the confidentiality and integrity of affected websites and their users. Successful exploitation allows attackers to execute arbitrary scripts in the context of the vulnerable site, which can lead to session hijacking, theft of sensitive user data, defacement of web pages, or redirection to malicious sites. Since the vulnerability requires authenticated access at the Candidate level or higher, attackers must have some level of legitimate access, which may limit exploitation but still poses a serious threat in environments where user accounts are numerous or poorly managed. The scope change in the CVSS vector indicates that the attack can affect components beyond the plugin itself, potentially impacting the entire WordPress site and its users. Organizations relying on WP JobHunt for job listings or recruitment may face reputational damage, loss of user trust, and potential regulatory consequences if user data is compromised. The absence of known exploits in the wild reduces immediate risk but does not eliminate the possibility of future attacks, especially as threat actors often target popular CMS plugins.

Mitigation Recommendations

To mitigate CVE-2025-7781, organizations should first monitor for and apply any official patches or updates released by the WP JobHunt plugin developers as soon as they become available. In the absence of patches, administrators should implement strict input validation and output encoding for the 'cs_job_title' parameter, either by customizing the plugin code or using security plugins that enforce content sanitization. Restricting user privileges to the minimum necessary can reduce the risk by limiting who can inject malicious scripts. Employing a Web Application Firewall (WAF) with rules designed to detect and block XSS payloads targeting this parameter can provide an additional layer of defense. Regularly auditing user accounts for suspicious activity and enforcing strong authentication policies will help prevent unauthorized access. Website owners should also educate users about the risks of XSS and monitor logs for unusual behavior indicative of exploitation attempts. Finally, consider isolating or sandboxing user-generated content areas to limit the impact of potential script execution.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-07-17T23:20:30.661Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68e8f247395901574383ec0a

Added to database: 10/10/2025, 11:47:19 AM

Last enriched: 2/26/2026, 4:36:12 PM

Last updated: 3/24/2026, 10:47:05 PM

Views: 146

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses