dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-12098

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
The Academy LMS – WordPress LMS Plugin for Complete eLearning Solution plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.3.8 via the 'enqueue_social_login_script' function. This makes it possible for unauthenticated attackers to extract sensitive data including the Facebook App Secret if Facebook Social Login is enabled.

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

The Academy LMS WordPress plugin versions up to 3.3.8 expose sensitive data through the 'enqueue_social_login_script' function. This function improperly handles the Facebook App Secret, making it accessible to unauthenticated attackers when Facebook Social Login is enabled.

MitigationUpdate Academy LMS plugin to version 3.3.9 or later. If immediate patching is not possible, disable Facebook Social Login functionality until the update can be 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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 Academy LMS plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Academy LMS. Note the version number displayed, or check the plugin header in wp-content/plugins/academy/index.php
    Affected if The installed version is 3.3.8 or lower (any version up to and including 3.3.8)
  2. Verify Facebook Social Login is enabled
    Navigate to Academy LMS settings in WordPress admin: Academy > Settings > General > Social Login. Check if Facebook option is toggled ON or configured with App ID/Secret
    Affected if Facebook Social Login is enabled or configured with Facebook App credentials in the plugin settings

You are affected if Academy LMS plugin version is 3.3.8 or lower AND Facebook Social Login is enabled in the plugin settings, as this combination exposes the Facebook App Secret to unauthenticated attackers.

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 Academy LMS plugin to version 3.3.9 or later. If immediate patching is not possible, disable Facebook Social Login functionality until the update can be applied.

Recommended fix Moderate confidence

Update Academy LMS to version 3.3.9 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find the Academy LMS plugin in the list
  4. 4. If an update is available, click 'Update Now' to update to the latest version (version 3.3.9 or later)
  5. 5. Verify the update completed successfully
  6. 6. Confirm that Facebook Social Login functionality continues to work as expected after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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