VernissageWordPress extension · Vernissage Project
CVE-2015-9477
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 Vernissage theme 1.2.8 for WordPress has insufficient restrictions on option updates.
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 Vernissage theme 1.2.8 for WordPress contains an authorization flaw where the theme's option update functionality lacks proper capability checks, allowing authenticated users with low privileges (such as subscribers) to modify theme settings that should require administrator-level access.
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
VernissageWordPress extension
= 1.2.8CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 if Vernissage theme is installedNavigate to WordPress admin > Appearance > Themes, or inspect the /wp-content/themes/ directory for a folder named 'vernissage' or similarAffected if The Vernissage theme folder exists in the WordPress themes directory
-
Verify the installed theme versionCheck the theme's style.css file in the theme folder for the 'Version:' header, or look in WordPress admin under Appearance > Themes > Theme DetailsAffected if The version is 1.2.8 exactly (or if the version cannot be determined and the theme appears to be Vernissage)
-
Confirm WordPress user roles existCheck WordPress users list at Users > All Users in admin, or query the wp_users and wp_usermeta tables in the databaseAffected if There are user accounts with 'Subscriber' role or other low-privilege roles enabled on the site
-
Check if theme options functionality is accessibleAttempt to access theme options page (typically at /wp-admin/themes.php?page=theme_options or similar), or inspect the theme's PHP files for option update handlers (look for 'update_option' or 'theme_options' in theme files)Affected if The theme provides an options/settings page that can be accessed by authenticated users
-
Check authentication settingsReview WordPress site settings at Settings > General > Membership, or check if anyone can register (Settings > General > Membership: 'Anyone can register' is checked)Affected if The site allows user registration or has subscriber-level accounts active
Your environment is affected if the Vernissage theme version 1.2.8 is installed and active, with any authenticated user accounts (especially subscribers or users with low privileges) able to access the site.
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 to a patched version of the Vernissage theme that includes proper authorization checks for option updates, or remove/disable the vulnerable theme if no update is available.
Fix this in Vernissage
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-2015-9477 — 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-2015-9477 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