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

CVE-2025-30577

HIGH · 7.1 CVSS v3.1 Published 2025-03-24
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 mendibass Browser Address Bar Color browser-address-bar-color allows Stored XSS.This issue affects Browser Address Bar Color: from n/a through <= 3.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 Mendibass Browser Address Bar Color extension enables attackers to inject malicious scripts that persist (Stored XSS) within the extension's settings or display functionality. The lack of CSRF protection allows forged requests from malicious sites to modify the extension's stored data with attacker-controlled content.

MitigationUpdate the extension to a patched version once available. Until then, disable the extension or limit usage to trusted sites only. The fix requires implementing anti-CSRF tokens and proper input sanitization before storing and rendering extension data.

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. Identify if the extension is installed
    Open your browser's extensions management page (chrome://extensions for Chrome/Chromium, about:addons for Firefox) and look for 'Mendibass Browser Address Bar Color' in the list of installed extensions.
    Affected if The extension appears in your list of installed extensions.
  2. Locate the installed version number
    On the extensions management page, enable 'Developer mode' (Chrome/Chromium) or click the gear icon (Firefox), then find the version number displayed next to 'Mendibass Browser Address Bar Color' in the extension details.
    Affected if You can retrieve a version number for this extension.
  3. Check extension storage for unexpected content
    Open the browser's developer tools (F12), go to the Application tab (Chrome) or Storage tab (Firefox), expand 'Extension Storage' or 'IndexedDB', look for the Mendibass extension's storage and inspect any stored settings, colors, or custom values for suspicious script tags, JavaScript URIs, or encoded payloads.
    Affected if Extension storage contains unexpected HTML, script tags, or data that was not entered by you.
  4. Review extension settings page for tampering
    If the extension provides a settings or options page (usually accessible via the extension's icon or a link on chrome://extensions), open it and verify that all color values, custom messages, or display text appear as you configured them and contain no injected content.
    Affected if Settings page displays unexpected text, scripts, or altered values you did not create.
  5. Audit recent browser history for exploitation indicators
    Check your browser history for visits to untrusted or suspicious websites that may have triggered the CSRF attack. Look for any requests made to the extension's internal pages or storage APIs originating from those sites.
    Affected if You visited untrusted websites while the extension was installed and notice unexplained changes to extension settings afterward.

You are affected if the Mendibass Browser Address Bar Color extension is installed and its stored settings contain unexpected or attacker-controlled content that was not explicitly set by you.

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 extension to a patched version once available. Until then, disable the extension or limit usage to trusted sites only. The fix requires implementing anti-CSRF tokens and proper input sanitization before storing and rendering extension data.

Recommended fix Moderate confidence

Latest version of Browser Address Bar Color plugin (newer than 3.3)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Browser Address Bar Color' plugin
  4. 4. Check if an update is available for this plugin
  5. 5. If an update is available, update to the latest version that addresses the CSRF vulnerability
  6. 6. Verify the update was successful and the plugin is functioning correctly

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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