dbcve.org
InjobWordPress extension · Sfwebservice

CVE-2025-1315

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-07
Fix available
A fix is available. Upgrade to after 3.5.1 or later.
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
The InWave Jobs plugin for WordPress is vulnerable to privilege escalation via password reset in all versions up to, and including, 3.5.1. This is due to the plugin not properly validating a user's identity prior to updating their password. This makes it possible for unauthenticated attackers to change arbitrary user's passwords, including administrators, and leverage that to gain access to their account.

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 confidence

The InWave Jobs WordPress plugin fails to validate user identity before allowing password changes in its password reset functionality. This allows unauthenticated attackers to reset arbitrary user passwords (including administrators) by manipulating the reset mechanism.

MitigationUpdate to the latest patched version of the plugin if available; otherwise remove the plugin. Immediately reset passwords for all administrator accounts as a precaution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
InjobWordPress extension
Affected:<= 3.5.1

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. Locate the InWave Jobs plugin installation
    Check your WordPress wp-content/plugins/ directory for a folder named 'inwave-jobs', 'injob', or 'sfwebservice-injob'. Also check via WordPress admin: Plugins > Installed Plugins and look for 'InWave Jobs' or 'Injob' in the list.
    Affected if The plugin folder or listing exists in your WordPress installation
  2. Identify the installed plugin version
    Open the main plugin file (usually inwp-content/plugins/[plugin-folder]/inwave-jobs.php or similar) and look for the 'Version' header in the plugin comments at the top. Alternatively, check wp-content/plugins/[plugin-folder]/readme.txt for the version number.
    Affected if The version is 3.5.1 or lower, or if no version is displayed and the plugin is present (assume affected)
  3. Verify the password reset functionality is accessible
    Check if your site exposes the plugin's password reset endpoint. Common paths include /wp-login.php?action=rp (WordPress default) or plugin-specific endpoints. Inspect your site's login page for any custom password reset forms provided by the InWave Jobs plugin.
    Affected if The plugin's user registration/login/password reset features are enabled and accessible on the site
  4. Identify WordPress users created via the plugin
    In WordPress admin, go to Users > All Users and review user accounts. The InWave Jobs plugin may create its own user accounts separate from standard WordPress users. Note any users with roles that could be affected by unauthorized password resets.
    Affected if There are user accounts on the site, particularly administrator accounts, that could be targeted via the password reset flaw

Your environment is affected if the InWave Jobs (Injob) plugin version 3.5.1 or lower is installed and active on your WordPress site, exposing the password reset functionality to unauthenticated attackers.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.5.1
Interim mitigation

Update to the latest patched version of the plugin if available; otherwise remove the plugin. Immediately reset passwords for all administrator accounts as a precaution.

Recommended fix Moderate confidence

Injob plugin version 3.5.2 or latest available release

  1. Check current Injob plugin version in WordPress admin under Plugins > Installed Plugins
  2. Backup the WordPress database and files before making changes
  3. Navigate to Plugins > Installed Plugins > Injob and click 'Update now' if version 3.5.2 or later is available
  4. If no update is available, check the WordPress plugin repository or themeforest.net for the latest version
  5. After updating, verify that the new version is active and the site functions normally
  6. Consider force-resetting passwords for administrator accounts as a precaution

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Injob Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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