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

CVE-2025-49453

HIGH · 7.1 CVSS v3.1 Published 2025-06-06
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 Jatinder Pal Singh BP Profile as Homepage bp-profile-as-homepage allows Stored XSS.This issue affects BP Profile as Homepage: from n/a through <= 1.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 · high confidence

CSRF vulnerability in the BP Profile as Homepage WordPress plugin allows attackers to inject stored XSS payloads by tricking authenticated administrators into submitting malicious requests. The lack of CSRF token validation on admin settings pages enables cross-site request forgery, which can lead to persistent malicious script execution when other users view affected pages.

MitigationImplement nonces/CSRF tokens on all form submissions and AJAX actions within the plugin, and ensure all user inputs are properly sanitized before storage and output.

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 installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, locate 'BP Profile as Homepage' or 'bp-profile-as-homepage', and note the version number displayed. Alternatively, check the plugin's main PHP file in wp-content/plugins/bp-profile-as-homepage/ for the Version header comment.
    Affected if The plugin is installed and the version is at or below the vulnerable version range (check against official WordPress repository for patch version).
  2. Confirm plugin is active
    In WordPress admin > Plugins, verify that BP Profile as Homepage is activated. The vulnerability only affects active plugin installations.
    Affected if The plugin is active on the WordPress site.
  3. Inspect admin settings code for CSRF protection
    Access the plugin directory via file manager or FTP, locate the file handling admin settings (commonly in includes/admin.php, admin-settings.php, or similar), and search for 'wp_nonce', 'nonce', 'verify_nonce', or 'check_admin_referer' functions around form submissions.
    Affected if No nonce verification or CSRF token validation is found in the admin settings processing code.
  4. Check settings output for sanitization
    Examine the plugin files that render or output the BP Profile settings (functions that display saved options), looking for apply_filters, echo, print, or similar output statements. Check if user-supplied values are passed through sanitization functions like sanitize_text_field, esc_attr, or esc_html before output.
    Affected if Settings values are output without proper sanitization, allowing stored XSS injection.
  5. Verify admin settings page accessibility
    Navigate to the plugin's settings page in WordPress admin (usually under Settings > BuddyPress Profile as Homepage or similar), attempt to save configuration changes, and confirm the page processes form submissions.
    Affected if The admin settings page exists and accepts form submissions without requiring additional confirmation.

A user is affected if the BP Profile as Homepage plugin is active, lacks CSRF nonce validation on its admin settings forms, and outputs stored settings without proper sanitization, allowing authenticated administrators to be tricked into injecting persistent malicious scripts.

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 nonces/CSRF tokens on all form submissions and AJAX actions within the plugin, and ensure all user inputs are properly sanitized before storage and output.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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