Skip to main content
WordPress plugin recordReviewed

Advanced Custom Fields vulnerability records, and the field settings that affect who can read the data

Show in REST API, an options page's Capability, the acf shortcode and a per-field editor setting each affect who can read ACF field data.

Where to read each without saving, and how to read a record printed with more than one edition.

Advanced Custom Fields vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 27 records for Advanced Custom Fields. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.

Check the patched version for your edition

Worked out from data retrieved on .

Some records list more than one edition of Advanced Custom Fields, each with its own version line. Use the patched version shown for the edition you run.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. Advanced Custom Fields (ACF) <= 6.7.0 - Incorrect Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via User Query Parameter Injection

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.7.0

    Patched versions: 6.7.1

    Update to at least version 6.7.1.

  2. Advanced Custom Fields <= 6.8.10 - Authenticated (Contributor+) Information Exposure

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.8.10

    Patched versions: 6.8.11

    Update to at least version 6.8.11.

  3. Advanced Custom Fields 6.2.0 - 6.8.10 - Authenticated (Contributor+) Insecure Direct Object Reference

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • From version 6.2.0 up to and including 6.8.10

    Patched versions: 6.8.11

    Update to at least version 6.8.11.

  4. Advanced Custom Fields (ACF®) <= 6.8.10 - Unauthenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 6.8.10

    Patched versions: 6.8.11

    Update to at least version 6.8.11.

  5. Advanced Custom Fields <= 6.8.10 - Missing Authorization

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.8.10

    Patched versions: 6.8.11

    Update to at least version 6.8.11.

Show 22 older records
  1. Advanced Custom Fields (ACF®) <= 6.8.1 - Unauthenticated Arbitrary Post Modification via Front-End Form '_post_title' and '_post_content' Parameters

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 6.8.1

    Patched versions: 6.8.2

    Update to at least version 6.8.2.

  2. Advanced Custom Fields (ACF®) <= 6.8.1 - Missing Authorization

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 6.8.1

    Patched versions: 6.8.2

    Update to at least version 6.8.2.

  3. Advanced Custom Fields (ACF®) <= 6.7.0 - Unauthenticated Missing Authorization to Arbitrary Post/Page Disclosure via AJAX Field Query Parameters

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 6.7.0

    Patched versions: 6.7.1

    Update to at least version 6.7.1.

  4. Advanced Custom Fields <= 6.4.2. - HTML Injection

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.1)
    Affected versions
    • All versions up to and including 6.4.2

    Patched versions: 6.4.3

    Update to at least version 6.4.3.

  5. Advanced Custom Fields <= 6.3.8 & Secure Custom Fields <= 6.3.6.2 - Authenticated (Admin+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.4)

    Advanced Custom Fields (ACF®)

    Affected versions
    • All versions up to and including 6.3.6.2

    Patched versions: 6.3.6.3

    Update to at least version 6.3.6.3.

    Advanced Custom Fields

    Affected versions
    • All versions up to and including 6.3.6
    • Version 6.3.7 only
    • Version 6.3.8 only

    Patched versions: 6.3.9

    Update to at least version 6.3.9.

  6. Advanced Custom Fields <= 6.3.8 - Authenticated (Admin+) Limited Arbitrary Function Call

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.1)

    Advanced Custom Fields (ACF®)

    Affected versions
    • All versions up to and including 6.3.6.2

    Patched versions: 6.3.6.3

    Update to at least version 6.3.6.3.

    Advanced Custom Fields

    Affected versions
    • All versions up to and including 6.3.6
    • Version 6.3.7 only
    • Version 6.3.8 only

    Patched versions: 6.3.9

    Update to at least version 6.3.9.

  7. Advanced Custom Fields <= 6.3.5 - Authenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.5)
    Affected versions
    • All versions up to and including 6.3.5

    Patched versions: 6.3.6

    Update to at least version 6.3.6.

  8. Advanced Custom Fields <= 6.2.10 - Authenticated (Contributor+) Arbitrary Custom Field Access

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.2.10

    Patched versions: 6.3.0

    Update to at least version 6.3.0.

  9. Advanced Custom Fields <= 6.2.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via Custom Field

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 6.2.4

    Patched versions: 6.2.5

    Update to at least version 6.2.5.

  10. Advanced Custom Fields 6.1 - 6.1.7 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.4)
    Affected versions
    • From version 6.1 up to and including 6.1.7

    Patched versions: 6.1.8

    Update to at least version 6.1.8.

  11. Advanced Custom Fields (Free and Pro) 5.8.10 to 5.12.5 & 6.0.0 to 6.1.5 - Reflected Cross-Site Scripting via 'post_status'

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • From version 5.8.10 up to and including 5.12.5
    • From version 6.0.0 up to and including 6.1.5

    Patched versions: 5.12.6, 6.1.6

    Update to at least the patched version for your release line: 5.12.6, 6.1.6.

  12. Advanced Custom Fields <= 6.0.7 - Authenticated (Contributor+) PHP Object Injection

    Published:
    Last updated:
    Severity:
    High (CVSS 8.8)
    Affected versions
    • All versions up to and including 5.12.4
    • From version 6.0.0 up to and including 6.0.7

    Patched versions: 5.12.5, 6.1.0

    Update to at least the patched version for your release line: 5.12.5, 6.1.0.

  13. Advanced Custom Fields <= 6.0.2 - Authenticated (Contributor+) Information Disclosure

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.0.2

    Patched versions: 6.0.3

    Update to at least version 6.0.3.

  14. Advanced Custom Fields <= 5.12.2 - File Upload

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 5.12.2

    Patched versions: 5.12.3

    Update to at least version 5.12.3.

  15. Advanced Custom Fields <= 5.12 - Authenticated Information Disclosure

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.5)
    Affected versions
    • All versions before 5.12.1

    Patched versions: 5.12.1

    Update to at least version 5.12.1.

  16. Advanced Custom Fields <= 5.10 - Missing Authorization on Option Changes

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions before 5.11

    Patched versions: 5.11

    Update to at least version 5.11.

  17. Advanced Custom Fields <= 5.10 - Missing Authorization to Information Disclosure

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions before 5.11

    Patched versions: 5.11

    Update to at least version 5.11.

  18. Advanced Custom Fields <= 5.10 - Missing Authorization to Information Disclosure

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.5)
    Affected versions
    • All versions before 5.11

    Patched versions: 5.11

    Update to at least version 5.11.

  19. Advanced Custom Fields <= 5.8.11 - Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions before 5.8.12

    Patched versions: 5.8.12

    Update to at least version 5.8.12.

  20. Advanced Custom Fields <= 5.7.11 - PHP Object Injection

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    Affected versions
    • All versions up to and including 5.7.11

    Patched versions: 5.7.12

    Update to at least version 5.7.12.

  21. Advanced Custom Fields <= 5.7.7 - Author+ Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    Affected versions
    • All versions before 5.7.8

    Patched versions: 5.7.8

    Update to at least version 5.7.8.

  22. Advanced Custom Fields <= 3.5.1 - Remote Code Execution via Remote File Inclusion

    Published:
    Last updated:
    Severity:
    Low (CVSS 3.8)
    Affected versions
    • All versions up to and including 3.5.1

    Patched versions: 3.5.2

    Update to at least version 3.5.2.

Check Advanced Custom Fields on a live site

Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.

What Advanced Custom Fields stores, and who reaches its screens

Advanced Custom Fields, or ACF, has a WordPress.org listing headed "Advanced Custom Fields (ACF®)" with the byline "By WP Engine".

The listing says fields can be added all over WordPress, including posts, pages, users, taxonomy terms, media, comments and even custom options pages. The vendor's security principles page says the values are stored in either associated meta tables or the WordPress options table, depending on where a field group is displayed.

The listing's changelog refers to frontend forms built with acf_form() and to frontend form submissions containing field data. The vendor's REST API guide says POST requests can update any ACF fields and require authentication. The vendor's settings reference describes ACF's capability setting as the "Capability used for ACF post types and if the current user can see the ACF menu item", with manage_options as its default.

Advanced Custom Fields vulnerabilities by title, edition and version line

The records in the history on this page are the ones the source data files under the slug advanced-custom-fields.

Where a record lists more than one edition, the history prints each edition's name with its own affected range and patched versions field, so copy those names exactly into your notes.

Phrases that recur in the titles include Stored Cross-Site Scripting, Information Disclosure and PHP Object Injection, and the access they state includes Unauthenticated, Authenticated (Contributor+) and Authenticated (Admin+). Three cases need care:

  • CVE-2024-49593 has a title ending "Authenticated (Admin+) Stored Cross-Site Scripting". The history prints its editions separately: "Advanced Custom Fields (ACF®)", all versions up to and including 6.3.6.2, patched in 6.3.6.3, and "Advanced Custom Fields", all versions up to and including 6.3.6, version 6.3.7 only and version 6.3.8 only, patched in 6.3.9.
  • CVE-2023-30777, whose title ends "Reflected Cross-Site Scripting via 'post_status'", lists versions from 5.8.10 up to and including 5.12.5 and from 6.0.0 up to and including 6.1.5, with 5.12.6 and 6.1.6 as patched versions.
  • CVE-2023-1196, whose title ends "Authenticated (Contributor+) PHP Object Injection", lists all versions up to and including 5.12.4, and from 6.0.0 up to and including 6.0.7, with 5.12.5 and 6.1.0 as patched versions. On the 6.0 line the fields say nothing about the versions between 6.0.7 and 6.1.0.

Advanced Custom Fields update status

Set the update guidance at the top of the history beside the fields of each record that matches your version. Before an update, also read the changelog on the WordPress.org listing, which marks security fixes with lines that begin with the word Security.

Reading ACF settings on a live site without saving

On a site you are authorised to review, open field groups, post types and options pages only to read them, and leave without pressing Save Changes, Update or any sync, import or export control.

Where an Advanced Configuration toggle is off, write that down rather than switching it on.

Plugin name, version and update route

Find the ACF row on the Plugins screen, whose Description column gives the version number and the plugin author name. 1 min read

Field groups and where they are defined

The vendor's field group guide says that to create a field group, you hover over ACF in the WordPress admin and select Field Group from the menu. 1 min read

REST API exposure

The vendor's REST API guide says field groups are not visible in the WP REST API by default, and that visibility is enabled for a specific field group by clicking Show in REST API on its Group Settings tab: list every group with it on. 1 min read

Options pages

The vendor's options page guide says the Options Pages UI was introduced in ACF PRO 6.2, and that to access it you hover over or click on ACF and select "Option Pages". 1 min read

Editor permissions and field access

On the Users screen, read the Role column, or click each role's filter link, to see which accounts hold each role. 1 min read

Field settings and theme code an ACF version does not reach

An installed ACF version that falls inside an affected range in the history matches a known record.

It cannot tell you whether anyone has exploited the flaw, which groups have Show in REST API on, whether the acf shortcode is on, which fields allow access in the editor UI, or which capability guards each options page.

Nor does it reach the theme. The security principles page says that by default ACF does not perform any escaping when using get_field(), and that users are therefore required to escape fields on output in their template or themes when using get_field or get_sub_field.

In a WordPress security audit, a contributor test account saves a draft containing script, and the audit confirms the script is stripped before an editor previews that draft.

Frequently asked questions

Only records the source data files under the slug advanced-custom-fields appear in the history, and that filing does not settle whether a record also applies to ACF PRO. The vendor's How to Update guide says that for a manual update the ACF PRO plugin files are downloaded from your account, and that its Plugins page update method is also available for ACF PRO, but only when an active licence is present. It says the licence key can be entered on the "ACF -> Updates" admin page.

The vendor's How to Update guide says versions of ACF 6.3.8 and later, and any version of ACF hosted on WP Engine or Flywheel, can be updated via the Plugins page in the WordPress admin. It says versions prior to 6.3.8 should be updated via a one-time download, and that once that is complete, plugin updates will appear in the WordPress admin as usual.

Not according to the vendor's security principles page, which makes one exception: field groups or individual fields made available through the REST API.

The vendor's security principles page says ACF will attempt to use the unfiltered_html capability to ensure only admins can store "potentially unsafe HTML", but that it is possible for users of contributor level or higher to bypass this protection using other WordPress provided methods of updating post meta. For this reason, it says, field values should be escaped on output too.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.

Data source and licence

The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.

Copyright 2012-2026 Defiant Inc.

Applies to every record listed below.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Copyright 1999-2026 The MITRE Corporation

Applies to 25 of the 27 records listed below.

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

Source records