dbcve.org
Wp Photo Album PlusWordPress extension · Wppa

CVE-2023-49813

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to after 8.5.02.005 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in J.N. Breetvelt a.K.A. OpaJaap WP Photo Album Plus allows Stored XSS.This issue affects WP Photo Album Plus: from n/a through 8.5.02.005.

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

Stored Cross-site Scripting (XSS) vulnerability in WP Photo Album Plus plugin allows authenticated attackers to inject malicious JavaScript code through unsanitized input. The payload gets stored in the database and executes when administrative users or visitors view affected pages containing the photo album content.

MitigationUpdate WP Photo Album Plus to the latest patched version once available, or implement proper input validation and output encoding on all user-supplied data before rendering. Review and sanitize any user-generated content fields within the plugin.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Photo Album PlusWordPress extension
Affected:<= 8.5.02.005

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check the installed version of WP Photo Album Plus
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins > WP Photo Album Plus, and note the version number displayed
    Affected if The installed version is 8.5.02.005 or lower
  2. Identify user input fields in the plugin
    Locate forms or input areas where users can submit content to the photo album (such as photo descriptions, album names, or caption fields)
    Affected if The plugin accepts user-supplied text input without visible sanitization indicators in the admin interface
  3. Inspect the database for stored scripts
    Query the WordPress database tables where plugin data is stored (typically tables prefixed with wp_wppa) and examine text fields for script tags, javascript:, or on* event handlers
    Affected if Database entries contain unsanitized HTML or JavaScript code that could execute in a browser
  4. Review pages rendering album content
    Visit frontend pages that display photo albums and view the page source to see how user-submitted content is rendered
    Affected if User-provided text from album fields is output to HTML without apparent encoding

A user is affected if they have WP Photo Album Plus version 8.5.02.005 or lower installed AND the plugin's user input fields are accessible to authenticated users, or if malicious scripts are already present in the database.

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
Upgrade available Upgrade to a release after 8.5.02.005
Interim mitigation

Update WP Photo Album Plus to the latest patched version once available, or implement proper input validation and output encoding on all user-supplied data before rendering. Review and sanitize any user-generated content fields within the plugin.

Recommended fix Moderate confidence

Latest stable version of WP Photo Album Plus (version 8.5.02.006 or higher)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'WP Photo Album Plus' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running on a version newer than 8.5.02.005
  6. 6. Test the affected functionality (photo uploads/comments) to confirm the XSS vulnerability is resolved
  7. 7. Clear any caching plugins or server-side caches after the update

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

Fix this in Wp Photo Album Plus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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