CVE-2025-10850
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 · uneditedThe Felan Framework plugin for WordPress is vulnerable to improper authentication in versions up to, and including, 1.1.4. This is due to the hardcoded password in the 'fb_ajax_login_or_register' function and in the 'google_ajax_login_or_register' function. This makes it possible for unauthenticated attackers to log in as any existing user on the site, if they registered with facebook or google social login and did not change their password. CVE-2025-23504 is likely a duplicate of this issue.
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 confidenceThe Felan Framework WordPress plugin versions up to 1.1.4 contain hardcoded passwords in the 'fb_ajax_login_or_register' and 'google_ajax_login_or_register' functions, enabling unauthenticated attackers to bypass authentication and log in as any existing user who registered via Facebook or Google social login without changing their password.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check Felan Framework plugin versionAccess your WordPress installation via file manager or FTP, navigate to /wp-content/plugins/ and locate the felan-framework folder. Open the main plugin PHP file (typically named felan-framework.php or similar) and look for the 'Version' header in the plugin comment block. Alternatively, go to WordPress Admin > Plugins > Installed Plugins and find Felan Framework in the list.Affected if The installed version is 1.1.4 or any earlier version.
-
Verify social login is enabledIn WordPress Admin, navigate to the Felan Framework plugin settings. Look for Facebook login and Google login configuration options. Check if either 'fb_ajax_login_or_register' or 'google_ajax_login_or_register' features are activated or enabled.Affected if Either Facebook social login, Google social login, or both are enabled in the plugin settings.
-
Inspect vulnerable authentication functionsAccess the Felan Framework plugin files via file manager or FTP. Navigate to the includes or functions folder within the plugin directory. Search for the functions named 'fb_ajax_login_or_register' and 'google_ajax_login_or_register' in the PHP files. Examine the code for hardcoded password strings or authentication bypass logic.Affected if These functions exist in the plugin code and contain hardcoded password values or allow unauthenticated access.
You are affected if the Felan Framework plugin version is 1.1.4 or earlier AND social login (Facebook or Google) is enabled, as the hardcoded passwords in those functions can be exploited for unauthorized access.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the Felan Framework plugin to a version beyond 1.1.4 immediately; if no patched version is available, disable the plugin and force-password-reset all users who registered via social login to prevent account takeover.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-10850 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10850 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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