Missing AuthorizationWeakness · CWE-862

CVE-2025-39536

HIGH · 8.2 CVSS v3.1 Published 2025-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in Chimpstudio JobHunt Job Alerts allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects JobHunt Job Alerts: from n/a through 3.6.

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 · moderate confidence

This is a Missing Authorization vulnerability in the JobHunt Job Alerts WordPress plugin. The plugin fails to properly verify user permissions before allowing access to or modification of job alert resources, allowing attackers to exploit incorrectly configured access control security levels to access or manipulate alerts they should not have permission to view or modify.

MitigationImplement proper authorization checks on all job alert endpoints to verify the requesting user has permission to access or modify the specific resource before executing any action.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the JobHunt Job Alerts plugin installation
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'jobhunt-job-alerts' or similar, or query the wp_options table for the option_name 'active_plugins' to see if the plugin is listed
    Affected if The plugin folder exists or the plugin is listed in active_plugins option
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually jobhunt-job-alerts.php) and look for the Version header comment at the top of the file, or check the plugins list in WordPress admin under Plugins > Installed Plugins
    Affected if The version number returned is within any known vulnerable version range for this CVE
  3. Verify job alerts functionality is enabled
    Check WordPress options table for plugin-specific settings, or log into WordPress admin and navigate to the plugin settings page to confirm job alerts feature is active
    Affected if Job alerts feature is enabled and accessible to users
  4. Inspect access control on alert endpoints
    Review the plugin PHP code for functions handling job alert access (typically functions with 'alert', 'get_alert', 'update_alert', or 'delete_alert' in the name) and check if they include current_user_can(), wp_verify_nonce(), or similar authorization checks before processing requests
    Affected if No authorization checks are found before accessing or modifying alert resources
  5. Check user role configuration for alert permissions
    If the plugin defines custom capabilities, review the wp_options table or plugin code for capability definitions related to job alerts, then verify which user roles have these capabilities using a user role editor or database query
    Affected if Users without proper roles can access or modify alerts they should not have access to

A user is affected if the JobHunt Job Alerts plugin is installed with the vulnerable feature enabled and the plugin lacks proper authorization checks on job alert endpoints, allowing unauthorized access to or manipulation of alerts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks on all job alert endpoints to verify the requesting user has permission to access or modify the specific resource before executing any action.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-39536 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-39536 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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