dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-23537

HIGH · 7.1 CVSS v3.1 Published 2025-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in קידום ובניית אתרים add custom google tag manager add-custom-google-tag-manager allows Stored XSS.This issue affects add custom google tag manager: from n/a through <= 1.0.3.

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

A CSRF vulnerability in the add-custom-google-tag-manager WordPress plugin (versions <=1.0.3) allows authenticated attackers to inject malicious JavaScript via crafted requests, resulting in stored XSS that executes in administrator browsers when viewing the affected plugin settings.

MitigationUpdate the plugin to the latest version, audit admin accounts for compromise, and remove any malicious scripts stored in the plugin's database options; also implement anti-CSRF tokens in all plugin forms.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 plugin is installed and get version
    Go to WordPress admin > Plugins > Installed Plugins, locate 'Custom Google Tag Manager' or 'add-custom-google-tag-manager' and read the version number displayed
    Affected if The installed version is 1.0.3 or lower, or the version displayed as '1.0.3' without a higher version shown
  2. Confirm plugin is active
    Check the Plugins screen to see if the plugin shows as 'Active' rather than 'Inactive' or 'Not installed'
    Affected if The plugin is active and running on the site
  3. Inspect plugin database options for stored scripts
    Query the WordPress options table (wp_options) for option_name containing 'google_tag_manager' or the plugin's specific option names, then examine the option_value for any script tags, iframe tags, or encoded JavaScript that you did not intentionally configure
    Affected if The plugin options contain unexpected script tags, encoded payloads, or markup you did not add
  4. Review plugin settings page in admin
    Navigate to the plugin's settings page in wp-admin (usually under Settings or a dedicated menu item) and view the page source or inspect elements to see if any unexpected JavaScript executes or is present in the form fields
    Affected if Viewing the plugin settings page triggers unexpected JavaScript execution or displays content you did not input

You are affected if the plugin is installed, active, and running version 1.0.3 or lower, or if suspicious script tags are found stored in the plugin's options.

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 the latest version, audit admin accounts for compromise, and remove any malicious scripts stored in the plugin's database options; also implement anti-CSRF tokens in all plugin forms.

Recommended fix Moderate confidence

Update to the latest version available in the WordPress plugin repository (version > 1.0.3)

  1. Log in to the WordPress admin dashboard.
  2. Navigate to Plugins > Installed Plugins.
  3. Locate 'add custom google tag manager' and update to the latest version available (ensure the version is greater than 1.0.3).
  4. After updating, verify the plugin version in the plugins list to confirm the update was successful.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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