Sermon BrowserWordPress extension · Sermon Browser Project
CVE-2016-10897
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 sermon-browser plugin before 0.45.16 for WordPress has multiple XSS issues.
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 sermon-browser WordPress plugin before version 0.45.16 contains multiple Cross-Site Scripting (XSS) vulnerabilities. These allow attackers to inject malicious scripts into web pages that are viewed by other users, potentially stealing session cookies or performing actions on behalf of authenticated users.
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
Sermon BrowserWordPress extension
< 0.45.16CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Locate the sermon-browser plugin filesCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'sermon-browser' or similar naming convention. If the folder exists, the plugin is installed.Affected if The sermon-browser plugin folder exists in the WordPress plugins directory.
-
Determine the installed plugin versionOpen the main PHP file of the sermon-browser plugin and look for the version header in the plugin comment block (typically at the top of the file). Compare this version number to 0.45.16.Affected if The version number found is less than 0.45.16 (for example, 0.45.15, 0.45.14, etc.).
-
Verify the plugin is activeCheck the WordPress database table wp_options for the option_name containing 'active_plugins' or use the WordPress admin dashboard to see if sermon-browser appears in the list of active plugins.Affected if The sermon-browser plugin appears in the active plugins list.
-
Confirm the plugin is accessible on the siteAttempt to access the sermon-browser functionality through the web browser by visiting common plugin paths or checking if sermon-related pages load on the frontend of the WordPress site.Affected if Sermon Browser pages or functionality are accessible and load without errors on the website.
A user is affected if the sermon-browser plugin is installed, active on the site, and the installed version is lower than 0.45.16.
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 data0.45.16
Update the sermon-browser plugin to version 0.45.16 or later to receive the security patches for the XSS vulnerabilities.
Fix this in Sermon Browser
Scoped from the published advisory
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10897 — 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-2016-10897 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