✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Wordfence Login Security: 2FA & login attempt tables

Wordfence Login Security stores 2FA secrets in wp_wfls_2fa_secrets, settings in wp_wfls_settings, and login activity in wp_wfLogins. SleekView reads all of them so enrolment, failures, and CAPTCHA outcomes sit in one queryable workspace.

♾️ Lifetime License available

SleekView table view for Wordfence Login Security

Track 2FA enrolment and login activity side by side

Wordfence Login Security, the standalone login plugin from the Wordfence team, keeps 2FA enrolment records in wp_wfls_2fa_secrets, plugin and role settings in wp_wfls_settings and wp_wfls_role_counts, and authentication attempts in the shared wp_wfLogins table. The default admin presents per-user 2FA status in one screen, recent logins in another, and CAPTCHA configuration in a third, with no native cross-filter between them.

SleekView reads each table directly so the three become one workspace. Sort users by 2FA enrolment state and last login. Filter wp_wfLogins to failed attempts on accounts that haven't enrolled. Pull role-level enrolment counts from wp_wfls_role_counts alongside actual recent logins to spot the gap between policy and reality.

Inline actions, like resetting a user's 2FA secret or forcing re-enrolment, route through Wordfence Login Security's own functions, so the plugin's audit trail stays correct. Saved views scoped per role let support staff verify enrolment without holding the keys to the settings, and let a security lead build a one-look enrolment audit for the team.

Workflow

From three screens to one enrolment audit

1

Connect the wfls tables

SleekView registers wp_wfls_2fa_secrets, wp_wfls_settings, wp_wfls_role_counts, and the shared wp_wfLogins as sources.
2

Build the enrolment view

Pick user, role, 2FA method, last login, and failed attempts. Save it as the team's go-to 'Admins missing TOTP' view and reopen it before any policy change.
3

Scope per role

Give support staff a read-only enrolment view, and grant security leads inline reset rights. Plugin settings stay restricted to administrators.
4

Act inline

Reset a TOTP secret, invalidate recovery codes, or send a re-enrolment prompt from a row. Writes go through Wordfence Login Security's own functions.

Sample columns

A typical Wordfence Login Security audit view

Users with their 2FA enrolment state, last login, and failed attempts in one row.
Source: wp_wfls_2fa_secrets + wp_wfls_settings + wp_wfls_role_counts + wp_wfLogins
User Role 2FA Last login Failed 24h Status
alex@studio.co Editor TOTP Apr 24 0 Enrolled
ria@design.io Author Recovery only Apr 23 2 Partial
tom@hello.dev Administrator TOTP Apr 24 5 Review
mia@brew.coop Subscriber None Apr 20 7 Not enrolled

Comparison

Default Wordfence Login Security admin vs SleekView

Default Wordfence Login Security

  • 2FA status, role policies, and wp_wfLogins live on separate screens
  • Hard to combine failed attempts with unenrolled accounts in one filter
  • Role-level counts from wp_wfls_role_counts aren't joinable with actual user rows
  • No native saved views for things like 'Admins without TOTP this month'
  • Bulk reminders or forced re-enrolment require row-by-row navigation

SleekView

  • Reads wp_wfls_2fa_secrets, wp_wfls_settings, and wp_wfLogins together
  • Filter to unenrolled admins with failed attempts in the last 24 hours
  • Inline reset of 2FA secrets via Wordfence Login Security's own functions
  • Save views like 'Admins missing TOTP' and reopen them with one click
  • Compare wp_wfls_role_counts policy with real enrolment to spot the gap

Features

What SleekView gives you for Wordfence Login Security

2FA enrolment as a real table

wp_wfls_2fa_secrets becomes a first-class source, joined to wp_users and wp_wfLogins so enrolment, last login, and recent failures land in one row.

Filter by role and CAPTCHA outcome

Combine role, 2FA state, and failed-attempt count to surface the accounts that need a reminder. Useful before forcing role-wide enrolment policies.

Inline reset and re-enrol

Reset a user's TOTP secret or revoke a recovery code from the same row. Writes go through Wordfence Login Security's actions so the audit trail stays clean.

Audience

Who uses SleekView for Wordfence Login Security

Security leads enforcing 2FA policies

Audit enrolment across roles in one table, compare wp_wfls_role_counts with actual rows, and reach 100 percent admin coverage before flipping a forced policy.

Support staff

Verify a user's 2FA state and last login from one row, reset a lost TOTP secret inline, and confirm the change appears in wp_wfls_2fa_secrets without leaving the table.

Auditors and compliance reviewers

Export filtered enrolment and login views for evidence. The CSV preserves user, role, 2FA state, and failed-attempt counts exactly as shown.

The bigger picture

Why 2FA rollouts stall without a real enrolment view

Most 2FA rollouts fail at the same place: the gap between policy and reality. Wordfence Login Security records both sides of that gap, role-level expectations in wp_wfls_role_counts and per-user enrolment in wp_wfls_2fa_secrets, alongside actual login activity in wp_wfLogins. The default admin shows each of those separately, which is fine for a single user lookup but slow for an audit.

The moment you need to know which administrators logged in last week without TOTP enrolled, the only answer is clicking through user lists by hand. SleekView reads the three tables as one workspace and lets the security lead build that audit as a saved view. Support staff can use a read-only version of the same view to verify a user's enrolment state during a support call, while a forced policy is being prepared.

The plugin keeps writing the data; SleekView just lets the people responsible for the policy read it in the order and shape they need. Once enrolment is visible at a glance, the gap closes quickly.

Questions

Common questions about SleekView for Wordfence Login Security

Yes. Wordfence Login Security is the free standalone plugin, and SleekView reads its wp_wfls_2fa_secrets, wp_wfls_settings, and wp_wfls_role_counts tables along with the shared wp_wfLogins table. No premium licence is needed for SleekView to surface this data.

 

Yes. SleekView triggers Wordfence Login Security's own reset action from a row, so the secret in wp_wfls_2fa_secrets is regenerated through the plugin's normal flow, recovery codes are invalidated, and the change is reflected in the plugin's own user list.

 

wp_wfls_role_counts tracks how many users in each role have enrolled. SleekView exposes it as a joinable source, so a single view can show policy intent (for example, all administrators must enrol) next to actual enrolment counts.

 

No. SleekView only reads what Wordfence Login Security already stores. Writes happen exclusively through the plugin's own functions, so the plugin remains the authoritative source for 2FA state, secrets, and login attempts.

 

Yes. Any filtered view exports to CSV from the table header. The export honours column order and active filters, useful for SOC2 evidence or a security review report.

 

Yes. CAPTCHA outcomes are recorded in wp_wfLogins alongside login attempts. SleekView exposes that as a filterable column so accounts repeatedly tripping CAPTCHA are easy to spot.

 

Yes. Saved views can be assigned per role, so support staff get a view scoped to their region or team, while a security lead sees the full enrolment table. Settings remain restricted by Wordfence Login Security's own capability checks.

 

Yes. Login Security data is per site, and SleekView respects the active scope. A network admin can build cross-subsite enrolment views; a subsite admin sees only their own users.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView