dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-54190

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-16
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
Unauthenticated Broken Access Control in Envira Photo Gallery <= 1.12.5 versions.

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

Unauthenticated Broken Access Control vulnerability in Envira Photo Gallery plugin versions 1.12.5 and below allows unauthenticated attackers to access functionality or data that should require authorization. The CVSS 6.5 indicates moderate impact likely involving unauthorized access to sensitive photo gallery data or administrative functions.

MitigationUpgrade Envira Photo Gallery to the latest version, or if no patch exists, implement web application firewall rules to restrict access to the vulnerable endpoints and audit the plugin's authorization checks.

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
Low

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

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 Envira Photo Gallery plugin is installed
    Locate the plugin directory in the WordPress installation (typically wp-content/plugins/envira-gallery) and verify the main plugin file exists. Alternatively, check the WordPress admin under Plugins > Installed Plugins for Envira Photo Gallery.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    Open the main plugin file (envira-gallery.php) and locate the version header in the plugin comment block (e.g., 'Version: 1.12.5'). Or view the version displayed in the WordPress admin Plugins page.
    Affected if The version number is 1.12.5 or lower
  3. Verify plugin is active
    Check WordPress admin under Plugins > Installed Plugins to confirm Envira Photo Gallery status shows 'Active'.
    Affected if The plugin is active and running
  4. Test for unauthenticated access to gallery data
    Send a direct HTTP request to common admin AJAX endpoints (wp-admin/admin-ajax.php) or API endpoints used by Envira Gallery without including valid authentication cookies or headers. Observe if the request succeeds when it should require a logged-in user.
    Affected if The plugin responds to unauthenticated requests that should require authorization (e.g., returns gallery data, configuration, or allows CRUD operations without login)

You are affected if Envira Photo Gallery version 1.12.5 or lower is installed and active, and unauthenticated access to gallery data or administrative functions is possible 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Envira Photo Gallery to the latest version, or if no patch exists, implement web application firewall rules to restrict access to the vulnerable endpoints and audit the plugin's authorization checks.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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