Gallery PhotoblocksWordPress extension · Wpchill
CVE-2022-37407
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 · uneditedMultiple Authenticated Stored Cross-Site Scripting (XSS) vulnerabilities in WPChill Gallery PhotoBlocks plugin <= 1.2.6 at WordPress.
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 confidenceAuthenticated stored XSS vulnerability in WPChill Gallery PhotoBlocks plugin allows malicious JavaScript injection via plugin settings or gallery content. The injected script persists and executes when other users access 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
Gallery PhotoblocksWordPress extension
<= 1.2.6CVSS 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.
-
Verify PhotoBlocks plugin is installedNavigate to WordPress admin > Plugins and look for 'Gallery PhotoBlocks' or 'photoblocks' in the installed plugins listAffected if Plugin appears in the WordPress plugins directory
-
Check installed version numberIn Plugins list, click 'View Details' on PhotoBlocks or inspect the plugin header in /wp-content/plugins/photoblocks/includes/functions.php for 'Version:' valueAffected if Version displayed is 1.2.6 or lower
-
Confirm plugin is activeIn WordPress admin > Plugins, check if PhotoBlocks shows 'Active' status or verify in database wp_options where option_name = 'active_plugins'Affected if Plugin is active and enabled on the site
-
Inspect gallery content for suspicious scriptsReview existing galleries in PhotoBlocks > All Galleries for any <script> tags, javascript: URLs, or event handlers (onclick, onload, etc.) in image titles, descriptions, or custom code fieldsAffected if Any gallery contains unrecognized JavaScript code or suspicious HTML attributes
-
Check plugin settings for injected codeGo to PhotoBlocks > Settings and examine all input fields for encoded or plain JavaScript payloads, particularly in custom CSS/JS fields or gallery metadataAffected if Settings contain unexpected script tags or JavaScript code not added by an administrator
A user is affected if the PhotoBlocks plugin is installed, active, and running version 1.2.6 or lower, or if evidence of unauthorized script injection exists in galleries or settings.
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 dataUpdate PhotoBlocks plugin to version newer than 1.2.6. If no update available, disable the plugin or restrict administrative access until a patch is released.
Fix this in Gallery Photoblocks
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-2022-37407 — 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-2022-37407 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