dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-27008

HIGH · 7.5 CVSS v3.1 Published 2025-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Missing Authorization vulnerability in NotFound Unlimited Timeline unlimited-timeline allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Unlimited Timeline: from n/a through < 1.6.1.

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

Missing Authorization vulnerability in NotFound Unlimited Timeline plugin allows attackers to access functionality not properly constrained by Access Control Lists (ACLs). This broken access control enables unauthorized users to perform actions that should require elevated privileges.

MitigationUpgrade Unlimited Timeline to version 1.6.1 or later which contains proper authorization constraints. Verify that all administrative functions require appropriate authentication after upgrade.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Identify installed Unlimited Timeline plugin version
    Access your WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate the 'Unlimited Timeline' plugin by NotFound, and record the version number displayed in the plugin details
    Affected if The installed version is lower than 1.6.1 or the version cannot be determined (plugin may be present but corrupted)
  2. Check plugin file version header via filesystem
    If admin access is unavailable, access the server filesystem and open the main plugin file in wp-content/plugins/unlimited-timeline/ (typically unlimited-timeline.php or similar), locate the 'Version:' header comment, and note the version number
    Affected if The version header shows a version lower than 1.6.1 or is absent
  3. Test for unauthenticated admin AJAX access
    Send a direct HTTP request to wp-admin/admin-ajax.php with common plugin action parameters (such as action=timeline_save, timeline_delete, or timeline_admin_) without providing authentication cookies or credentials
    Affected if The endpoint returns successful data or performs actions rather than returning an authentication error (401/403)
  4. Inspect plugin for missing capability checks
    Review the plugin PHP source code for functions that handle admin or privileged operations, specifically looking for current_user_can() calls before executing sensitive actions
    Affected if Sensitive functions lack capability checks or the checks are only present on some but not all admin actions

Your environment is affected if the Unlimited Timeline plugin version is below 1.6.1 and administrative or privileged functions can be accessed or executed without authentication.

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 Unlimited Timeline to version 1.6.1 or later which contains proper authorization constraints. Verify that all administrative functions require appropriate authentication after upgrade.

Recommended fix Moderate confidence

1.6.1

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Unlimited Timeline' plugin by NotFound
  4. 4. If the plugin shows an update available, click 'Update Now' to upgrade to version 1.6.1 or latest version
  5. 5. Alternatively, manually download version 1.6.1 or later from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the new version number in the plugins list

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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