dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-39581

HIGH · 8.5 CVSS v3.1 Published 2026-06-16
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 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
Subscriber SQL Injection in WP Sessions Time Monitoring Full Automatic <= 1.1.4 versions.

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 WordPress plugin 'WP Sessions Time Monitoring Full Automatic' allows authenticated users with Subscriber role to inject malicious SQL queries through unsanitized input parameters.

MitigationUpgrade to version 1.1.5 or later; if no patch is available, disable the plugin until a fix is released.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WP Sessions Time Monitoring Full Automatic' in the installed plugins list
    Affected if plugin is not present in the installed plugins list
  2. Identify installed version
    Click on the plugin in the WordPress plugins list to view the version number, or inspect the plugin's main PHP file header for the Version field
    Affected if installed version is lower than 1.1.5 (the fixed version)
  3. Verify plugin is active
    Check the plugins list status - the plugin must be active for the vulnerability to be exploitable
    Affected if plugin is active and version is below 1.1.5
  4. Confirm user role access exists
    Review WordPress user roles to determine if any Subscriber-level accounts exist or can be created; the SQL injection is exploitable by any authenticated user with Subscriber role
    Affected if Subscriber role users exist and plugin is vulnerable

Environment is affected if the WP Sessions Time Monitoring Full Automatic plugin is installed, active, and running a version lower than 1.1.5 with Subscriber-level user accounts present.

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 version 1.1.5 or later; if no patch is available, disable the plugin until a fix is released.

Recommended fix Moderate confidence

Latest available version of WP Sessions Time Monitoring Full Automatic (version > 1.1.4)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'WP Sessions Time Monitoring Full Automatic' plugin
  4. 4. Check the current installed version
  5. 5. If the installed version is <= 1.1.4, update the plugin to the latest available version
  6. 6. Verify the update completes successfully
  7. 7. Test that the plugin functionality works as expected after update

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

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-2026-39581 — 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-2026-39581 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