CVE-2019-14797
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 · uneditedThe 10Web Photo Gallery plugin before 1.5.23 for WordPress has authenticated stored XSS.
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 confidenceThe 10Web Photo Gallery plugin before version 1.5.23 for WordPress contains an authenticated stored XSS (Cross-Site Scripting) vulnerability. Attackers with valid WordPress credentials (subscriber-level or higher) can inject malicious JavaScript into gallery content that persists on the server and executes when other users view the affected pages.
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< 1.5.23CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed version of 10Web Photo Gallery pluginNavigate to WordPress admin > Plugins > Installed Plugins. Locate '10Web Photo Gallery' in the list and read the version number displayed beneath the plugin name. Alternatively, inspect the plugin main file (photo-gallery/photo-gallery.php) for the 'Version' header comment.Affected if Version number is less than 1.5.23 (for example, 1.5.22, 1.5.21, etc.)
-
Verify plugin is activeIn the WordPress Plugins admin page, confirm the 10Web Photo Gallery plugin shows as 'Active' rather than 'Inactive' or 'Must-Use'.Affected if Plugin is active AND version is below 1.5.23
-
Identify user roles with gallery accessIn WordPress admin > Users, review which roles exist. The vulnerability is exploitable by any user with subscriber-level access or higher, as long as they can access the gallery creation/editing functionality.Affected if Any user role below Administrator (such as Subscriber, Contributor, or Author) is permitted access to the gallery plugin features, and the plugin version is vulnerable.
-
Inspect gallery content for suspicious entries (post-compromise)Navigate to Photo Gallery > Galleries in the admin panel. Review each gallery's title, description, and embedded images for unexpected script tags, javascript: URLs, or HTML event attributes (onload, onerror, onmouseover, etc.). Check the page source of published galleries if you have direct access.Affected if Any gallery contains unescaped HTML or JavaScript code that was not intentionally added by an administrator, indicating potential exploitation.
Your environment is affected if the 10Web Photo Gallery plugin is installed, active, and the installed version is before 1.5.23.
Generated from the published advisory. Verify against your own configuration.
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 data1.5.23
Update the 10Web Photo Gallery plugin to version 1.5.23 or later. Alternatively, disable the plugin until an update can be applied.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2019-14797 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-14797 in production — separate from our analysis above.
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.
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.
- 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