Simple FieldsWordPress extension · Simple Fields Project

CVE-2013-7476

HIGH · 8.8 CVSS v3.0 Published 2019-08-14
Fix available
A fix is available. Upgrade to 1.2 or later.
See remediation →
95/100
Remediation priority · Urgent
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 simple-fields plugin before 1.2 for WordPress has CSRF in the admin interface.

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

The simple-fields WordPress plugin before version 1.2 contains a Cross-Site Request Forgery (CSRF) vulnerability in its admin interface. This allows attackers to trick authenticated administrators into performing unintended actions via malicious requests, as the plugin fails to validate anti-CSRF tokens on admin operations.

MitigationUpdate the simple-fields plugin to version 1.2 or later which includes CSRF protection. Alternatively, add WordPress nonces to all admin forms and AJAX endpoints, and verify these nonces on form submission.

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
Simple FieldsWordPress extension
Affected:< 1.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 simple-fields plugin installation
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'simple-fields' or similar. Also check wp-content/mu-plugins/ if present.
    Affected if The simple-fields plugin folder exists in the WordPress installation.
  2. Identify the installed plugin version
    Open the main plugin file (usually simple-fields.php) and look for the version header in the plugin comment block, or check the readme.txt file for the 'Stable tag' entry.
    Affected if The version number found is less than 1.2 (e.g., 1.1.x, 1.0.x, or no version specified).
  3. Verify the plugin is active
    Log into the WordPress admin dashboard, go to Plugins > Installed Plugins, and check whether the simple-fields plugin is currently activated.
    Affected if The simple-fields plugin shows as 'Active' in the WordPress admin plugins list.
  4. Inspect admin forms for nonce field absence
    In the plugin PHP files (typically in the /inc/ or /classes/ folder within simple-fields), search for admin form definitions (HTML <form> tags) and check if they include a nonce field (wp_nonce_field, wp_nonce_url, or similar).
    Affected if Admin forms in the plugin code lack any wp_nonce_field or equivalent CSRF token generation calls.
  5. Inspect AJAX handlers for nonce verification
    Search the plugin PHP files for AJAX action handlers (add_action with 'wp_ajax_' or 'wp_ajax_nopriv_' hooks) and check if these handlers verify nonces using check_ajax_referer or wp_verify_nonce.
    Affected if AJAX endpoints registered by the plugin do not call check_ajax_referer or wp_verify_nonce to validate CSRF tokens.

You are affected if the simple-fields plugin is installed, active, and its version is below 1.2, with admin forms and AJAX handlers lacking CSRF token validation.

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.2 or later
Fixed in 1.2
Interim mitigation

Update the simple-fields plugin to version 1.2 or later which includes CSRF protection. Alternatively, add WordPress nonces to all admin forms and AJAX endpoints, and verify these nonces on form submission.

Fix this in Simple Fields Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-7476 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-7476 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