CVE-2025-7782
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WP JobHunt plugin for WordPress, used by the JobCareer theme, is vulnerable to unauthorized modification of data due to a missing capability check on the 'cs_update_application_status_callback' function in all versions up to, and including, 7.7. This makes it possible for authenticated attackers, with Candidate-level access and above, to inject cross-site scripting into the 'status' parameter of applied jobs for any user.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP JobHunt plugin for WordPress has a missing capability check on the 'cs_update_application_status_callback' function, allowing authenticated users with Candidate-level access to modify job application status data. Combined with insufficient sanitization of the 'status' parameter, this enables stored cross-site scripting (XSS) attacks where malicious scripts can be injected into job application status fields.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm WP JobHunt plugin is installedNavigate to WordPress admin > Plugins and verify the WP JobHunt plugin appears in the installed plugins list, or check the filesystem at /wp-content/plugins/ for the wp-jobhunt directoryAffected if The plugin is not installed on the WordPress site
-
Identify installed plugin versionIn WordPress admin > Plugins, find WP JobHunt and note the version number displayed, or check the plugin main file header for 'Version:' fieldAffected if Version is lower than 7.8 or the version cannot be determined
-
Locate the vulnerable callback functionAccess the site via FTP or file manager and examine the plugin files, specifically searching for 'cs_update_application_status_callback' function definition in the plugin codeAffected if The function exists in the plugin files (indicating the vulnerable code path is present)
-
Verify capability check is missingOpen the file containing 'cs_update_application_status_callback' and inspect whether 'current_user_can()' or proper capability verification appears before the status update logicAffected if No capability check or role verification is found before the status modification code
-
Check status parameter sanitization in outputSearch the plugin code for where the application status is displayed/output, and verify whether esc_html() or esc_attr() is used when rendering the status valueAffected if The status value is output without sanitization functions like esc_html() or esc_attr()
A user is affected if the WP JobHunt plugin is installed with a version lower than 7.8 and the vulnerable callback function exists without proper capability checks and output sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to version 7.8 or later once released. Until a patch is available, implement proper capability checks using current_user_can() and sanitize all output using functions like esc_html() and esc_attr() for the status parameter.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7782 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data