dbcve.org
Photo GalleryWordPress extension · 10web

CVE-2015-2324

MEDIUM · 5.4 CVSS v3.0 Published 2018-02-19
Fix available
A fix is available. Upgrade to 1.2.13 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Cross-site scripting (XSS) vulnerability in the filemanager in the Photo Gallery plugin before 1.2.13 for WordPress allows remote authenticated users with edit permission to inject arbitrary web script or HTML via unspecified vectors.

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

Cross-site scripting (XSS) vulnerability in the Photo Gallery plugin's filemanager allows authenticated users with edit permissions to inject arbitrary JavaScript or HTML. This is a stored XSS issue where malicious scripts can be persisted and executed when other users access the affected functionality.

MitigationUpdate Photo Gallery plugin to version 1.2.13 or later to patch the XSS vulnerability. Alternatively, disable the plugin if the update cannot be applied promptly.

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
Photo GalleryWordPress extension
Affected:< 1.2.13

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

CVSS:3.0/AV:N/AC:L/PR:L/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. Confirm Photo Gallery plugin is installed
    Navigate to the WordPress admin plugins page and locate 10web Photo Gallery in the list of installed plugins. Check if it shows as 'Active'.
    Affected if The plugin is installed and active, exposing the filemanager functionality.
  2. Identify the installed version
    In the WordPress plugins list, locate the version number displayed beneath the plugin name '10web Photo Gallery'. Alternatively, check the plugin's main file header for the 'Version' comment.
    Affected if The installed version is any version prior to 1.2.13 (for example, 1.2.12, 1.2.10, 1.0.5, etc.).
  3. Compare version to affected range
    Compare the identified version number against the affected range: any version less than 1.2.13 is vulnerable. Document whether the installed version falls within this range.
    Affected if The version is less than 1.2.13, meaning the XSS vulnerability is present in the filemanager.
  4. Verify filemanager is accessible
    Access the Photo Gallery plugin settings and confirm the filemanager feature is enabled. This is typically found under the plugin's configuration or media settings.
    Affected if The filemanager module is enabled and accessible to users, allowing the stored XSS to be triggered.
  5. Identify users with edit permissions
    Review WordPress user roles and permissions. Check for users assigned the Editor, Administrator, or custom roles with edit capabilities for the Photo Gallery plugin.
    Affected if Users with edit permissions exist who could potentially inject malicious scripts through the filemanager.

A user is affected if the 10web Photo Gallery plugin is installed with a version lower than 1.2.13, the filemanager is enabled, and users with edit permissions are present on the site.

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
Upgrade available Upgrade to 1.2.13 or later
Fixed in 1.2.13
Interim mitigation

Update Photo Gallery plugin to version 1.2.13 or later to patch the XSS vulnerability. Alternatively, disable the plugin if the update cannot be applied promptly.

Fix this in Photo Gallery Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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