dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-10570

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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 Sympl Repeater for ACF and Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via ACF repeater field values in all versions up to, and including, 2.3. This is due to insufficient input sanitization and output escaping in the symp_arfe_replace_content() function, which uses str_replace() to substitute raw ACF field values (retrieved via get_field()) directly into Elementor-rendered HTML without any escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 · high confidence

The Sympl Repeater for ACF and Elementor WordPress plugin (versions up to 2.3) contains a stored XSS vulnerability in the symp_arfe_replace_content() function. This function retrieves ACF field values via get_field() and uses str_replace() to insert them directly into Elementor-rendered HTML without any sanitization or escaping. Authenticated users with Author-level or higher permissions can inject malicious JavaScript into ACF repeater field values that will execute when other users access the affected pages.

MitigationUpdate the plugin to version 2.4 or later once available, or disable the plugin until a security patch is released. Audit existing pages using ACF repeater fields to identify and remove any malicious script injections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Confirm plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Sympl Repeater for ACF and Elementor' in the list
    Affected if The plugin is not installed or has been removed entirely
  2. Check plugin version
    On the Plugins page, click on the plugin to view its details, or check the plugin's main PHP file header for the Version constant. Compare against the affected range (versions up to 2.3)
    Affected if Installed version is 2.3 or below
  3. Verify plugin is active
    On the Plugins > Installed Plugins page, check if the plugin shows as 'Active'
    Affected if Plugin is active and running on the site
  4. Identify ACF repeater field usage
    Check if ACF (Advanced Custom Fields) with repeater field types is installed and being used alongside the Sympl Repeater plugin. Review page/post content that uses Elementor with ACF repeater fields
    Affected if ACF repeater fields are in use with Elementor pages and the vulnerable function symp_arfe_replace_content() is being called
  5. Audit ACF repeater field values for malicious scripts
    Access the WordPress admin and review ACF repeater field values in posts/pages. Look for suspicious script tags, event handlers (onclick, onerror, etc.), or encoded JavaScript in field contents
    Affected if Any ACF repeater field values contain unsanitized HTML or script tags that could execute when the page is viewed

You are affected if the Sympl Repeater for ACF and Elementor plugin is installed, active, and running version 2.3 or below while ACF repeater fields are being used with Elementor pages.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 2.4 or later once available, or disable the plugin until a security patch is released. Audit existing pages using ACF repeater fields to identify and remove any malicious script injections.

Recommended fix Moderate confidence

latest available version ( newer than 2.3 )

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Sympl Repeater for ACF and Elementor plugin
  4. Check if an update is available and update to the latest version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10570 — 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-2026-10570 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