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

CVE-2026-57675

HIGH · 7.1 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 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
Unauthenticated Cross Site Scripting (XSS) in WP Photo Album Plus <= 9.2.02.004 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 · high confidence

An unauthenticated Cross Site Scripting (XSS) vulnerability exists in the WP Photo Album Plus WordPress plugin versions 9.2.02.004 and below. Attackers can inject malicious JavaScript into web pages viewed by other users without requiring authentication, potentially leading to session hijacking, credential theft, or defacement.

MitigationUpdate WP Photo Album Plus to the latest version or apply vendor-supplied patch to properly sanitize and escape user input before output.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Verify WP Photo Album Plus is installed
    Check the WordPress plugin directory or access the plugins admin page to confirm WP Photo Album Plus is present and active
    Affected if Plugin is not installed or not active - not affected
  2. Identify installed plugin version
    Navigate to Plugins > Installed Plugins in WordPress admin, find WP Photo Album Plus, and read the version number displayed. Alternatively, check the plugin header in wp-content/plugins/wp-photo-album-plus/readme.txt or the main plugin PHP file for the Version tag
    Affected if Cannot determine version - status unknown
  3. Compare version against affected range
    Compare your installed version number to 9.2.02.004. Versions 9.2.02.004 and any version number lower than this are within the affected range
    Affected if Installed version is 9.2.02.004 or lower - environment is affected
  4. Verify unauthenticated access to plugin features
    Attempt to access plugin pages or parameters without logging in. The vulnerability is exploitable without authentication, so check if the plugin publicly exposes any parameters that could be manipulated
    Affected if Plugin allows unauthenticated parameter injection - exploitable

The environment is affected if WP Photo Album Plus is installed with version 9.2.02.004 or below and the plugin is accessible to unauthenticated users.

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 the latest version or apply vendor-supplied patch to properly sanitize and escape user input before output.

Recommended fix Moderate confidence

Latest version of WP Photo Album Plus (newer than 9.2.02.004)

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Find WP Photo Album Plus in the plugin list.
  4. 4. If there is an update available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is functioning correctly and clear any caching layers.

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