Modula Image GalleryWordPress extension · Wpchill
CVE-2020-9003
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 · uneditedA stored XSS vulnerability exists in the Modula Image Gallery plugin before 2.2.5 for WordPress. Successful exploitation of this vulnerability would allow an authenticated low-privileged user to inject arbitrary JavaScript code that is viewed by other users.
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 confidenceA stored XSS vulnerability in the Modula Image Gallery plugin for WordPress (versions before 2.2.5) allows authenticated low-privilege users to inject arbitrary JavaScript code into gallery content. This malicious script is persistently stored and executes when other users view the affected gallery 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
Modula Image GalleryWordPress extension
< 2.2.5CVSS 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 Modula Image Gallery is installedNavigate to WordPress admin dashboard > Plugins and locate the Modula Image Gallery plugin in the installed plugins listAffected if The Modula Image Gallery plugin appears in the installed plugins list
-
Check installed plugin versionIn the Plugins list, click on the plugin details or view the plugin file header (typically in modula.php) to read the Version numberAffected if The installed version is lower than 2.2.5 (for example: 2.2.4, 2.2.0, 1.x.x, etc.)
-
Identify existing galleriesNavigate to Modula Image Gallery in the WordPress admin sidebar and review the galleries list to see if any galleries have been createdAffected if One or more galleries exist in the Modula plugin
-
Confirm low-privilege user accessReview WordPress user roles and verify if any users with Subscriber, Contributor, or Author roles have access to create or edit Modula galleriesAffected if Low-privilege users (Subscriber, Contributor, Author) can access Modula gallery creation or editing features
The environment is affected if Modula Image Gallery plugin version is below 2.2.5 and any galleries exist on the site, particularly if low-privilege users can modify gallery content.
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 data2.2.5
Upgrade the Modula Image Gallery plugin to version 2.2.5 or later to remediate the stored XSS vulnerability.
Fix this in Modula Image Gallery
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9003 — 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-2020-9003 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