Missing AuthorizationWeakness · CWE-862

CVE-2026-1036

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-22

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

NVD · unedited

The Photo Gallery by 10Web – Mobile-Friendly Image Gallery plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the delete_comment() function in all versions up to, and including, 1.8.36. This makes it possible for unauthenticated attackers to delete arbitrary image comments. Note: comments functionality is only available in the Pro version of the plugin.

Technical summary

dbcve analysis · high confidence

This is a Broken Access Control vulnerability in the Photo Gallery by 10Web WordPress plugin. The delete_comment() function lacks proper capability checks, allowing unauthenticated attackers to delete arbitrary image comments via direct function calls. This affects only the Pro version where comments functionality exists.

MitigationUpdate the plugin to version 1.8.37 or later which should include proper authorization checks for the delete_comment() function. Until patched, consider disabling the comments feature in the Pro version settings.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm Photo Gallery by 10Web plugin is installed

Navigate to WordPress admin > Plugins and locate 'Photo Gallery by 10Web' or inspect the /wp-content/plugins/ directory for photo-gallery folders

Affected if The plugin is not installed in the WordPress environment
Verify the Pro version is in use

Check the plugins list for 'Photo Gallery Pro' or inspect /wp-content/plugins/ for a photo-gallery-pro directory; the vulnerability only affects the Pro version

Affected if Only the free version (photo-gallery) is installed, not the Pro version
Confirm comments functionality is enabled in the Pro settings

Go to Photo Gallery Pro settings in WordPress admin and locate the comments configuration; verify if the comments feature is turned on

Affected if Comments functionality is disabled in the plugin settings
Check the installed plugin version against the fixed release

In WordPress admin > Plugins, click on Photo Gallery Pro to view the version number, or open the main plugin PHP file and locate the 'Version' header comment

Affected if The installed version is earlier than 1.8.37 (the version that includes the fix)

A user is affected if they have Photo Gallery Pro installed with comments enabled and the plugin version is below 1.8.37

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update the plugin to version 1.8.37 or later which should include proper authorization checks for the delete_comment() function. Until patched, consider disabling the comments feature in the Pro version settings.

Recommended fix Moderate confidence

Latest version after 1.8.36 (check WordPress plugin repository for current release)

Log into the WordPress admin dashboard
Navigate to Plugins > Installed Plugins
Locate the 'Photo Gallery by 10Web' plugin
Check if an update is available and update to the latest version
Alternatively, navigate to Dashboard > Updates and update the plugin from there
Verify the update was successful by checking the plugin version

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

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-1036 — 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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1036 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-1036?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

Need this fixed?

Have this fixed 8 hrs · Moderate

Typical engagement from $1,420

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-1036 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References