dbcve.org
Wp Latest PostsWordPress extension · Joomunited

CVE-2016-10913

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-20
Fix available
A fix is available. Upgrade to 3.7.5 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 wp-latest-posts plugin before 3.7.5 for WordPress has XSS.

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

Cross-Site Scripting (XSS) vulnerability in the wp-latest-posts WordPress plugin versions prior to 3.7.5. The vulnerability allows attackers to inject malicious scripts into the plugin's output, likely through unsanitized user input in the frontend display of latest posts.

MitigationUpdate the wp-latest-posts plugin to version 3.7.5 or later to obtain the vendor patch that addresses the XSS vulnerability.

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
Wp Latest PostsWordPress extension
Affected:< 3.7.5

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

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

  1. Verify wp-latest-posts plugin is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'wp-latest-posts' or 'Joomunited Wp Latest Posts' in the plugin list
    Affected if The plugin is present in the WordPress installation
  2. Identify installed version
    In the Plugins list, find the wp-latest-posts entry and note the version number displayed beneath the plugin name
    Affected if The version number is less than 3.7.5 (for example, 3.7.4, 3.7.0, or any version below 3.7.5)
  3. Confirm active usage on frontend
    Check if the plugin shortcode [wp-latest-posts] or widget is being used on any pages, posts, or widget areas by reviewing content pages and the Appearance > Widgets section
    Affected if The plugin shortcode or widget is actively displayed on the website frontend
  4. Inspect plugin configuration
    Access the plugin settings via the WordPress admin menu (usually under 'Latest Posts' or 'Wp Latest Posts') and review any fields related to post display, titles, or custom content that accept user input
    Affected if The plugin settings contain custom titles, labels, or content fields that could accept unsanitized input and be rendered on the frontend

A user is affected if the wp-latest-posts plugin is installed with a version lower than 3.7.5 AND the plugin is actively rendering content on the frontend.

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 3.7.5 or later
Fixed in 3.7.5
Interim mitigation

Update the wp-latest-posts plugin to version 3.7.5 or later to obtain the vendor patch that addresses the XSS vulnerability.

Fix this in Wp Latest Posts 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-2016-10913 — 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-2016-10913 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