Read the docs
TI-2023-03981 Aliases CVE-2023-4307GHSA-pj3h-qmr5-3qpv

Lock User Account <= 1.0.3 - Arbitrary Account Lock/Unlock via CSRF

Priority MEDIUM 53Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA.

Summary

The Lock User Account WordPress plugin through 1.0.3 does not have CSRF check when bulk locking and unlocking accounts, which could allow attackers to make logged in admins lock and unlock arbitrary users via a CSRF attack

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00252 16th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA and NVD
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
UnknownLock User Accountup to 1.0.3—No fix listedCNA
  • Lock User Account VendorUnknown Affected up to 1.0.3 Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:teknigar:lock_user_account:*:*:*:*:*:wordpress:*:*up to 1.0.3VulnerableTeknigar
  • cpe:2.3:a:teknigar:lock_user_account:*:*:*:*:*:wordpress:*:* Versions up to 1.0.3 Vulnerable ·Teknigar

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2023-4307
  2. 2026-10-03 Alias added: GHSA-pj3h-qmr5-3qpv

References

Sources