dbcve.org
SchemaWordPress extension · Brainstormforce

CVE-2018-20977

MEDIUM · 6.1 CVSS v3.1 Published 2019-08-21
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The all-in-one-schemaorg-rich-snippets plugin before 1.5.0 for WordPress has XSS on the settings page.

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 confidence

Cross-Site Scripting (XSS) vulnerability in the all-in-one-schemaorg-rich-snippets WordPress plugin affecting versions prior to 1.5.0. The vulnerability exists on the plugin's settings page, likely due to insufficient input sanitization or improper output encoding of user-supplied data.

MitigationUpdate the all-in-one-schemaorg-rich-snippets plugin to version 1.5.0 or later to patch the XSS vulnerability. Before updating, backup the WordPress site and test the update in a staging environment if possible.

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
SchemaWordPress extension
Affected:< 1.5.0

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the plugin installation
    Check the wp-content/plugins directory for a folder named 'all-in-one-schemaorg-rich-snippets' or 'schema' or check via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder is not found, meaning the plugin is not installed
  2. Identify the installed version
    Open the main plugin PHP file (usually index.php or the plugin's main file) and look for the version comment/header, or check the version field in the plugin's main PHP file header comment
    Affected if The version displayed is less than 1.5.0 (e.g., 1.4.x, 1.3.x, etc.)
  3. Verify the plugin is active
    Check the WordPress admin under Plugins > Installed Plugins and confirm the plugin status shows as 'Active'
    Affected if The plugin is currently active on the site
  4. Confirm access to settings page
    Navigate to the plugin's settings page in the WordPress admin (usually under Settings or the plugin's own menu item)
    Affected if The settings page is accessible and the plugin is enabled

If the plugin is installed, active, and its version is below 1.5.0, the site is vulnerable to XSS on the settings page and should be updated.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.5.0 or later
Fixed in 1.5.0
Interim mitigation

Update the all-in-one-schemaorg-rich-snippets plugin to version 1.5.0 or later to patch the XSS vulnerability. Before updating, backup the WordPress site and test the update in a staging environment if possible.

Fix this in Schema Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-20977 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-20977 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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