dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-25367

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
Missing Authorization vulnerability in NooTheme CitiLights noo-citilights allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects CitiLights: from n/a through < 3.7.2.

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 the NooTheme CitiLights WordPress theme allows unauthenticated attackers to exploit incorrectly configured access control security levels. The issue stems from missing permission checks that should restrict certain functionality to authorized users only.

MitigationUpdate CitiLights theme to version 3.7.2 or later to obtain the vendor patch. If immediate update is not possible, review and enforce proper access control checks on sensitive theme functions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm CitiLights theme installation
    Navigate to WordPress admin panel under Appearance > Themes, or check the wp-content/themes/ directory for a folder named 'citi-lights', 'citiLights', or similar variant. Identify the exact folder name used.
    Affected if The CitiLights theme is installed, regardless of whether it is the active theme
  2. Locate the theme version
    In the theme directory, open the style.css file and locate the 'Version:' comment header in the file comments at the top. Also check functions.php for any version constants or variables.
    Affected if The version found is below 3.7.2 (e.g., 3.7.1, 3.6.x, etc.)
  3. Check for authorization callbacks in theme hooks
    Search the theme's functions.php and any included files for actions that handle user requests (add_action, add_filter). Look specifically for hooks using 'wp_ajax_nopriv_' which allow unauthenticated access, and verify if they include capability checks like current_user_can() before executing sensitive operations.
    Affected if Theme functions are accessible to unauthenticated users (wp_ajax_nopriv_ hooks) without proper permission checks like current_user_can()
  4. Inspect access control implementation
    Review theme PHP files for functions that should require authorization (such as settings saves, user data operations, or configuration changes). Search for the presence of authorization functions: current_user_can(), check_admin_referer(), wp_verify_nonce(), or similar permission verification calls.
    Affected if Sensitive theme functions lack authorization checks and can be invoked by any visitor without authentication

A user is affected if the CitiLights theme is installed with a version lower than 3.7.2 and exposes functionality accessible to unauthenticated users without proper permission verification.

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 CitiLights theme to version 3.7.2 or later to obtain the vendor patch. If immediate update is not possible, review and enforce proper access control checks on sensitive theme functions.

Recommended fix Moderate confidence

CitiLights version 3.7.2 or later

  1. 1. Update the CitiLights WordPress theme to version 3.7.2 or later through the WordPress dashboard (Appearance > Themes) or via the theme vendor's update mechanism
  2. 2. After updating, verify the theme version reflects 3.7.2 or higher in the theme settings or WordPress admin
  3. 3. Test the access control functionality to ensure the authorization controls are working as expected
  4. 4. If automatic updates are available, enable them to receive future security patches promptly
Caveat Review theme changelog for any deprecated features or styling changes that may affect your site after upgrading

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-2026-25367 — 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-2026-25367 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