dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-39477

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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 Sfwebservice InWave Jobs allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects InWave Jobs: from n/a through 3.5.8.

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 (broken access control) vulnerability in the InWave Jobs plugin's web service component (Sfwebservice). The vulnerability allows unauthenticated or unauthorized attackers to access sensitive functionality or data due to incorrectly configured access control security levels, enabling complete bypass of intended authorization checks.

MitigationImplement proper authorization checks on all web service endpoints, enforce role-based access control (RBAC), and audit access control configurations to ensure all protected resources require valid authorization tokens or session credentials.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify if InWave Jobs plugin is installed
    Locate the InWave Jobs plugin files in the web application's plugin directory (typically /wp-content/plugins/ or similar depending on the CMS/platform). Look for a folder named 'inwave-jobs' or similar.
    Affected if The plugin directory contains the InWave Jobs plugin files.
  2. Determine the installed plugin version
    Check the plugin's main PHP file or a version.php file within the InWave Jobs plugin folder for a version declaration. Compare the version number against any known affected versions.
    Affected if The installed version falls within an affected version range for this CVE.
  3. Locate the Sfwebservice component
    Search the plugin directory for files or folders named 'Sfwebservice', 'webservice', 'api', or similar service-related components. Check for endpoints under /sfwebservice/ or similar URL paths.
    Affected if The Sfwebservice component exists and is accessible within the plugin.
  4. Test web service endpoint authorization
    Send HTTP requests to known or suspected web service endpoints (such as /wp-json/inwave-jobs/v1/ or /sfwebservice/ endpoints) WITHOUT providing authentication credentials or valid authorization tokens. Observe if the request is accepted and returns sensitive data or functionality.
    Affected if Requests to web service endpoints succeed without authentication, returning data or functionality that should require authorization.
  5. Review access control configuration
    Examine the plugin's configuration files, particularly any XML or PHP files that define security levels, access control lists, or endpoint permissions. Look for settings that control anonymous or unauthenticated access to web services.
    Affected if Configuration files show that security levels are set too low (such as 'public' or 'none') for sensitive web service endpoints, or access control checks are missing.

A user is affected if they have the InWave Jobs plugin installed with the Sfwebservice component accessible without proper authorization checks.

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 web service endpoints, enforce role-based access control (RBAC), and audit access control configurations to ensure all protected resources require valid authorization tokens or session credentials.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-39477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-39477 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