Library ViewerWordPress extension · Pexlechris
CVE-2023-32102
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 · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Pexle Chris Library Viewer plugin <= 2.0.6 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 confidenceAuthenticated users with contributor+ role can inject malicious JavaScript through the Library Viewer plugin's input fields. The stored XSS executes when other users access the affected content, allowing session hijacking, defacement, or phishing.
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
Library ViewerWordPress extension
< 2.0.6.1CVSS 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.1/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 plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > Pexle Chris Library Viewer and note the version number displayedAffected if the version number is lower than 2.0.6.1
-
Identify contributor-plus usersGo to Users > All Users in WordPress admin and review the role column for accounts with Contributor, Author, Editor, or Administrator rolesAffected if any user account with contributor-level or higher access exists on the site
-
Inspect Library Viewer content for injected scriptsAccess the Library Viewer plugin settings or any published library content, then view the page source or use browser developer tools to examine input fields and stored content for script tags, event handlers, or suspicious encoded stringsAffected if script tags, javascript: URIs, or event handlers like onload/onerror are present in Library Viewer fields
-
Verify plugin is activeConfirm the Pexlechris Library Viewer plugin is enabled and the Library Viewer feature is publicly accessibleAffected if the plugin is active and its content pages are accessible to users
You are affected if the installed Library Viewer version is below 2.0.6.1 AND contributor-plus user accounts exist AND the plugin is active, as the XSS can only be exploited when authenticated users with contributor role or higher can access the plugin input fields.
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.
dbcve · scoped2.0.6.1
Update to the latest version of the Pexle Chris Library Viewer plugin. Until patched, restrict contributor-level user creation and monitor for suspicious content.
Library Viewer 2.0.6.1
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate the Library Viewer plugin by Pexle Chris
- Click 'Update now' if an update to version 2.0.6.1 or later is available, or manually upload the latest version from the WordPress plugin repository
- Verify the plugin version is 2.0.6.1 or higher after updating
- Test that the Library Viewer functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Library Viewer
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32102 — 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-2023-32102 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