dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-46455

CRITICAL · 9.3 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 →
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in IndigoThemes WP HRM LITE wp-hrm-lite-human-resource-management-system allows SQL Injection.This issue affects WP HRM LITE: from n/a through <= 1.1.

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

SQL injection vulnerability in IndigoThemes WP HRM LITE plugin allows attackers to inject malicious SQL commands via unsanitized input in HTTP parameters. The CVSS 9.3 indicates unauthenticated remote exploitation is possible.

MitigationUpgrade to a patched version of WP HRM LITE; until available, sanitize all database queries using prepared statements and validate/sanitize all user-supplied input.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 checks

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

  1. Confirm WP HRM LITE plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WP HRM LITE' by IndigoThemes in the installed plugins list; note whether it is activated
    Affected if Plugin is installed and activated
  2. Identify the installed plugin version
    In WordPress admin > Plugins > WP HRM LITE, click on the plugin name to view details; record the version number displayed
    Affected if Version is unknown or below the patched release (compare to vendor advisories)
  3. Check for exposed plugin endpoints
    Scan web server logs or use a directory enumeration tool to identify accessible URLs containing '/wp-content/plugins/wp-hrm-lite/' or 'hrm' paths; test common parameter names like 'id', 'user_id', 'search', 'emp_id'
    Affected if Plugin endpoints are publicly accessible without authentication
  4. Review HTTP logs for SQL injection patterns
    Examine Apache/Nginx access logs for requests to the plugin's PHP files containing SQL keywords (UNION, SELECT, INSERT, --, ;, ') in query parameters
    Affected if Malicious SQL patterns are present in recent HTTP requests to the plugin
  5. Verify database query logging
    Enable MySQL query logging or check existing security monitoring for unusual database activity from the web server user; look for queries containing unsanitized user input
    Affected if Unexpected or injection-style queries are logged from the application

A defender is affected if the WP HRM LITE plugin is installed, activated, publicly accessible, and running an unpatched version, or if SQL injection attempts are visible in HTTP or database logs.

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

Upgrade to a patched version of WP HRM LITE; until available, sanitize all database queries using prepared statements and validate/sanitize all user-supplied input.

Recommended fix Moderate confidence

Latest version available from IndigoThemes (version 1.2 or higher)

  1. 1. Confirm your current installed version of WP HRM LITE plugin by navigating to WordPress admin > Plugins
  2. 2. Check IndigoThemes official website or the WordPress plugin repository for the latest available version
  3. 3. Before upgrading, create a complete backup of your WordPress database and files
  4. 4. Test the upgrade in a staging environment if possible, as this is a critical plugin handling HR data
  5. 5. Upgrade to the latest version available from the vendor
  6. 6. After upgrade, verify the SQL injection vulnerability is resolved by testing relevant functionality or using a vulnerability scanner
  7. 7. Review user roles and permissions in the plugin settings post-upgrade to ensure proper access controls
Caveat Review plugin settings after upgrade as configuration changes may occur between versions

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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