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

CVE-2025-23508

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 OrigoThemes Extra Options – Favicons extra-options-favicons allows Stored XSS.This issue affects Extra Options – Favicons: from n/a through <= 1.1.0.

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

Cross-Site Request Forgery (CSRF) vulnerability in OrigoThemes Extra Options – Favicons plugin allows attackers to inject malicious JavaScript through Stored XSS. An attacker can trick an authenticated administrator into submitting a crafted request that stores malicious scripts in the plugin settings, which then execute when viewed by other users.

MitigationImplement anti-CSRF tokens (nonces) on all form submissions and properly sanitize/validate all user inputs before storing. Update to patched version if available; otherwise disable the plugin until fix is applied.

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 plugin is installed
    Navigate to WordPress admin dashboard > Plugins. Look for 'OrigoThemes Extra Options - Favicons' or 'Extra Options - Favicons' in the installed plugins list. Note the installed version displayed next to the plugin name.
    Affected if The plugin appears in the installed plugins list, regardless of version, as this indicates potential exposure to the vulnerability.
  2. Locate plugin files for code inspection
    Access the WordPress installation via file manager or FTP. Navigate to wp-content/plugins/ and look for a folder named 'extra-options-favicon', 'origo-extra-options', or similar containing 'favicon' in the name. Identify the main PHP file and any admin PHP files that handle form submissions.
    Affected if Plugin files exist in the plugins directory, indicating the plugin is active and its code can be analyzed for missing CSRF protections.
  3. Check for nonce verification in form handling
    Open the plugin's admin PHP files. Search for 'wp_nonce_field', 'check_admin_referer', 'wp_verify_nonce', or 'nonce' throughout the code. Examine any form submission handlers (POST/GET requests processing plugin settings).
    Affected if Form handling code lacks nonce verification functions, meaning the plugin does not validate that requests originate from legitimate admin sessions.
  4. Verify input sanitization on stored settings
    In the plugin's form processing code, locate where user inputs from $_POST or $_GET are saved to the database (update_option, add_option, or direct database inserts). Check if functions like sanitize_text_field, esc_attr, orwp_kses are applied before storage.
    Affected if User-supplied values from form inputs are stored without sanitization, allowing malicious scripts to be persisted in the database.
  5. Confirm settings page renders stored values unsafely
    If possible, access the plugin settings page in the WordPress admin. Inspect how saved values are output (view page source). Look for whether stored values are echoed without escaping functions like esc_html or esc_attr.
    Affected if Stored plugin settings are displayed in HTML pages without proper output escaping, causing stored XSS to execute when the settings page is viewed.

A user is affected if the OrigoThemes Extra Options - Favicons plugin is installed and its form submission handlers lack nonce verification combined with insufficient input sanitization and output escaping, allowing stored XSS injection via CSRF.

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 (nonces) on all form submissions and properly sanitize/validate all user inputs before storing. Update to patched version if available; otherwise disable the plugin until fix is applied.

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-23508 — 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-23508 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