dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-10095

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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 WP Photo Album Plus plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'subtext' parameter in all versions up to, and including, 9.1.13.005 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. A contributor-level attacker can embed the malicious [photo] shortcode in a post submitted for review, causing the stored payload to execute when an administrator or any other user views the post.

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 WP Photo Album Plus WordPress plugin fails to sanitize the 'subtext' parameter in the [photo] shortcode on input and escape it on output, allowing authenticated contributors to inject malicious JavaScript that persists in submitted posts and executes when administrators or other users view those pages.

MitigationUpdate WP Photo Album Plus to version 9.1.13.006 or later which properly sanitizes the 'subtext' parameter and escapes output to prevent XSS.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Confirm WP Photo Album Plus plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Photo Album Plus' in the list
    Affected if the plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In the plugins list, locate WP Photo Album Plus and note the version number displayed below the plugin name
    Affected if the version is below 9.1.13.006
  3. Search for usage of the [photo] shortcode with subtext parameter
    In WordPress admin, go to Posts or Pages and review content for instances of [photo ... subtext=...] shortcode, or search the database for posts containing 'subtext=' in the wp_posts table
    Affected if the shortcode with subtext parameter is present in any published content
  4. Inspect stored subtext values for potential malicious content
    Examine the subtext parameter values in the shortcode for suspicious patterns such as <script> tags, javascript: URIs, or event handlers like onload/onerror
    Affected if any subtext values contain unsanitized JavaScript code or HTML attributes
  5. Review contributor and author user accounts
    In WordPress admin, go to Users and check which roles exist; contributors and above have access to create content with shortcodes
    Affected if there are user accounts with contributor, author, editor, or administrator roles who can create or edit posts

A user is affected if WP Photo Album Plus version below 9.1.13.006 is installed AND the [photo] shortcode with the subtext parameter is used in any post or page content.

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 WP Photo Album Plus to version 9.1.13.006 or later which properly sanitizes the 'subtext' parameter and escapes output to prevent XSS.

Recommended fix Moderate confidence

Latest version of WP Photo Album Plus (version higher than 9.1.13.005)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find WP Photo Album Plus in the plugin list
  4. Check if an update is available and update to the latest version
  5. Verify the update was successfully applied

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