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

CVE-2025-48114

HIGH · 7.1 CVSS v3.1 Published 2025-05-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 Shayan Farhang Pazhooh ShayanWeb Admin FontChanger shayanweb-admin-fontchanger allows Stored XSS.This issue affects ShayanWeb Admin FontChanger: from n/a through <= 1.9.1.

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 ShayanWeb Admin FontChanger WordPress plugin (versions up to 1.9.1) allows attackers to inject malicious scripts through stored XSS by tricking authenticated administrators into triggering crafted requests.

MitigationImplement anti-CSRF tokens for all state-changing admin actions and properly sanitize/validate all user inputs to prevent stored XSS.

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 ShayanWeb Admin FontChanger plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'admin-font-changer' or similar, or list installed plugins via WP-CLI: wp plugin list --name='admin-font-changer'
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Check the installed plugin version
    Open the main plugin file (usually admin-font-changer.php) and look for the Version header in the plugin comment block, or run: wp plugin get admin-font-changer --field=version
    Affected if The reported version is 1.9.1 or lower
  3. Confirm administrator authentication is possible
    Verify that the WordPress site has user accounts with Administrator role who can access the plugin settings page under the WordPress admin dashboard
    Affected if Any user with Administrator role exists and can log in to the WordPress admin area
  4. Inspect plugin settings for stored XSS payloads
    Access the plugin settings page (usually under Settings > Font Changer or a dedicated admin menu item) and examine all input fields for any existing malicious script content, or query the wp_options table for option_names related to the plugin
    Affected if Any unsanitized user-supplied values are stored in the plugin settings database entries

The environment is affected if the ShayanWeb Admin FontChanger plugin is installed with version 1.9.1 or lower and an administrator can access its settings, as the CSRF-to-stored-XSS flaw can be triggered through crafted requests to these settings.

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

Implement anti-CSRF tokens for all state-changing admin actions and properly sanitize/validate all user inputs to prevent stored XSS.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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