dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-11758

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
The All in One Time Clock Lite plugin for WordPress is vulnerable to unauthorized access due to a missing authorization check in all versions up to, and including, 2.0.3. This is due to the plugin exposing admin-level AJAX actions to unauthenticated users via wp_ajax_nopriv_ hooks, while relying only on a nonce check without capability checks. This makes it possible for unauthenticated attackers to create published pages, create shift records with integrity issues, and download time reports containing PII (employee names and work schedules).

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 · high confidence

The All in One Time Clock Lite plugin for WordPress versions up to 2.0.3 exposes admin-level AJAX actions to unauthenticated users through wp_ajax_nopriv_ hooks, relying only on nonce checks without capability verifications. This allows unauthenticated attackers to create published pages, forge shift records, and exfiltrate PII including employee names and work schedules via time report downloads.

MitigationUpdate to version 2.0.4 or later which adds proper capability checks to AJAX endpoints. Ensure all wp_ajax_nopriv_ handlers verify user capabilities (current_user_can) before processing requests.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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. Verify plugin installation and version
    Check the installed version of 'All in One Time Clock Lite' plugin in WordPress (Plugins > Installed Plugins) or inspect plugin header in the main plugin file
    Affected if Version is 2.0.3 or earlier (the plugin is vulnerable up to version 2.0.3)
  2. Confirm AJAX endpoint exposure
    Test accessing wp-admin/admin-ajax.php with nopriv AJAX actions (such as aio_tc_create_page, aio_tc_save_shift, or aio_tc_download_report) without providing authentication cookies
    Affected if The endpoint returns a valid response rather than a 403 or redirect to login, indicating the handler executes without verifying user capabilities
  3. Inspect registered AJAX hooks
    Search plugin source code for wp_ajax_nopriv_ action registrations and verify they lack current_user_can checks before processing
    Affected if nopriv hooks exist without capability verification logic (current_user_can checks) in the callback handlers
  4. Test for unauthenticated time report access
    Attempt to trigger time report download functionality via AJAX without logging in, observing if PII (employee names, schedules) can be accessed
    Affected if The download or report generation completes and returns data without requiring admin-level authentication

The environment is affected if the All in One Time Clock Lite plugin version is 2.0.3 or earlier and unauthenticated AJAX requests to nopriv endpoints execute without capability checks.

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

Update to version 2.0.4 or later which adds proper capability checks to AJAX endpoints. Ensure all wp_ajax_nopriv_ handlers verify user capabilities (current_user_can) before processing requests.

Recommended fix Moderate confidence

All in One Time Clock Lite version 2.0.4 or latest available

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'All in One Time Clock Lite'
  4. Check the current installed version (should be 2.0.3 or below)
  5. Update the plugin to the latest available version (2.0.4 or higher)

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
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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