dbcve.org
Related PostsWordPress extension · Zemanta

CVE-2013-3477

MEDIUM · 6.8 CVSS v2.0 Published 2014-05-27
Fix available
A fix is available. Upgrade to after 1.3.1 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Cross-site request forgery (CSRF) vulnerability in the Related Posts by Zemanta plugin before 1.3.2 for WordPress allows remote attackers to hijack the authentication of unspecified users for requests that change settings via unknown vectors.

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 request forgery (CSRF) vulnerability in the Related Posts by Zemanta WordPress plugin before version 1.3.2 allows remote attackers to trick authenticated administrators into unknowingly submitting requests that modify plugin settings, due to missing or insufficient CSRF tokens or referer validation.

MitigationUpdate the Related Posts by Zemanta plugin to version 1.3.2 or later, which includes proper CSRF protection mechanisms. Verify all administrative settings remain correct after the update.

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
Related PostsWordPress extension
Affected:<= 1.3.1= 1.0= 1.1= 1.2= 1.3

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 Zemanta Related Posts plugin installation
    In your WordPress admin dashboard, go to Plugins > Installed Plugins and search for 'Zemanta' or 'Related Posts by Zemanta'. Alternatively, check the /wp-content/plugins/related-posts-by-zemanta/ directory on your server.
    Affected if The plugin directory exists or the plugin appears in your WordPress plugins list.
  2. Identify the installed plugin version
    In the WordPress admin, find the plugin in the Installed Plugins list and look for the version number displayed beneath the plugin name. If using FTP or file access, open the main plugin file (usually related-posts-by-zemanta.php) and locate the 'Version' header in the plugin metadata comments.
    Affected if The displayed version is 1.0, 1.1, 1.2, 1.3, or any version listed as 1.3.1 or lower.
  3. Verify the plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm the plugin shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is currently active on the WordPress site.
  4. Confirm admin user authentication context
    CSRF attacks against this plugin require an authenticated administrator to unknowingly submit a crafted request. Determine if any administrator-level users have active sessions or if the site has admin users.
    Affected if Administrator users exist and can access the WordPress admin panel while the vulnerable plugin is active.
  5. Compare your version to the affected range
    Cross-reference your identified version against the affected range: versions 1.0, 1.1, 1.2, 1.3, and any version through 1.3.1 are vulnerable. Version 1.3.2 contains the fix.
    Affected if Your installed version falls within 1.0 through 1.3.1 inclusive.

You are affected if the Related Posts by Zemanta plugin is installed, active, and running version 1.3.1 or lower, allowing unauthenticated remote attackers to trick administrators into modifying plugin settings via CSRF.

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 a release after 1.3.1
Interim mitigation

Update the Related Posts by Zemanta plugin to version 1.3.2 or later, which includes proper CSRF protection mechanisms. Verify all administrative settings remain correct after the update.

Fix this in Related 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-2013-3477 — 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-2013-3477 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