VYPR
High severity8.5NVD Advisory· Published Jun 16, 2026· Updated Jun 16, 2026

CVE-2026-39581

CVE-2026-39581

Description

SQL injection in WP Sessions Time Monitoring Full Automatic <=1.1.4 allows subscriber-level attackers to interact with the database.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

SQL injection in WP Sessions Time Monitoring Full Automatic <=1.1.4 allows subscriber-level attackers to interact with the database.

Vulnerability

The WP Sessions Time Monitoring Full Automatic plugin for WordPress versions 1.1.4 and earlier contains a SQL injection vulnerability exploitable by authenticated users with Subscriber-level access. The plugin fails to properly sanitize user-supplied input before using it in SQL queries, allowing an attacker to inject arbitrary SQL commands. [1]

Exploitation

An attacker needs a valid WordPress account with at least the Subscriber role. By sending crafted input to a vulnerable parameter, the attacker can inject malicious SQL statements. The vulnerability is expected to be used in mass-exploit campaigns targeting thousands of sites simultaneously. [1]

Impact

Successful exploitation allows the attacker to directly interact with the database, including reading sensitive information such as user credentials and other stored data. The attacker may also be able to modify or delete database contents, leading to further compromise. [1]

Mitigation

The vulnerability is fixed in version 1.1.5. Users should update to this version or later immediately. Patchstack has issued a mitigation rule to block attacks until the update is applied. No other workarounds are available. [1]

AI Insight generated on Jun 16, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.