dbcve.org
ExactmetricsWordPress extension · Monsterinsights

CVE-2023-23880

MEDIUM · 5.4 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 7.14.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in ExactMetrics plugin <= 7.14.1 versions.

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 confidence

Authenticated contributor+ users can inject malicious JavaScript via stored Cross-Site Scripting in the ExactMetrics WordPress plugin versions 7.14.1 and below. The vulnerability stems from insufficient input sanitization and output encoding, allowing script execution when other users view the injected content.

MitigationUpdate ExactMetrics to the latest version, or implement proper input validation and output escaping on all user-supplied data fields within the plugin.

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
ExactmetricsWordPress extension
Affected:< 7.14.2

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
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 checks

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

  1. Verify ExactMetrics plugin is installed
    Check your WordPress plugins directory for the ExactMetrics plugin folder, typically at /wp-content/plugins/exactmetrics/, or list installed plugins via WordPress admin under Plugins > Installed Plugins
    Affected if ExactMetrics plugin files are present on the server
  2. Check the installed ExactMetrics version
    Open the main plugin file (usually exactmetrics.php) in the plugin directory and locate the 'Version' header in the plugin comments, or view the version in WordPress admin under Plugins > Installed Plugins next to the ExactMetrics listing
    Affected if The reported version is 7.14.1 or lower (below 7.14.2)
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify ExactMetrics shows as 'Active', or check the wp_options table for option_name 'active_plugins' containing 'exactmetrics'
    Affected if ExactMetrics is currently activated on the site
  4. Identify contributor+ user accounts
    In WordPress admin, navigate to Users and review the role column for accounts with Contributor, Author, Editor, or Administrator roles, or query the wp_usermeta table joining with wp_users to list users with roles hierarchy_level 2 or higher
    Affected if Any user accounts with Contributor role or higher exist on the WordPress site

Your environment is affected if ExactMetrics version 7.14.1 or below is installed and active, and contributor-level or higher user accounts exist on the WordPress site.

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.

dbcve · scoped
Upgrade available Upgrade to 7.14.2 or later
Fixed in 7.14.2
Interim mitigation

Update ExactMetrics to the latest version, or implement proper input validation and output escaping on all user-supplied data fields within the plugin.

Recommended fix High confidence

ExactMetrics 7.14.2

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find ExactMetrics in the plugin list
  5. 5. If an update is available, click 'Update Now' to update to version 7.14.2 or later
  6. 6. Alternatively, download ExactMetrics 7.14.2 or later from the WordPress plugin repository
  7. 7. Deactivate the current ExactMetrics plugin
  8. 8. Upload and install the newer version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Exactmetrics 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-2023-23880 — 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-2023-23880 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