dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-23202

CRITICAL · 10.0 CVSS v4.0 Published 2025-01-17
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Bible Module is a tool designed for ROBLOX developers to integrate Bible functionality into their games. The `FetchVerse` and `FetchPassage` functions in the Bible Module are susceptible to injection attacks due to the absence of input validation. This vulnerability could allow an attacker to manipulate the API request URLs, potentially leading to unauthorized access or data tampering. This issue has been addressed in version 0.0.3. All users are advised to upgrade. There are no known workarounds for this vulnerability.

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 FetchVerse and FetchPassage functions in the Bible Module for ROBLOX lack input validation, allowing attackers to inject malicious content into API request URLs. This could enable unauthorized access to external APIs or manipulation of data returned to the game.

MitigationUpgrade to version 0.0.3 which includes proper input validation. No workarounds are available.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Bible Module is installed
    Check your Roblox place or game for any Script or ModuleScript named 'Bible', 'BibleModule', or similar that handles Bible verse/passage fetching. Look in ServerScriptService, ReplicatedStorage, or workspace for references to FetchVerse or FetchPassage functions.
    Affected if The Bible Module for Roblox is present in your game environment
  2. Determine the module version
    If the module is an external asset, check the asset version on the Roblox marketplace or your internal asset management system. Compare against version 0.0.3. If it's a local script, check the version comment or metadata at the top of the ModuleScript.
    Affected if The installed version is below 0.0.3 or the version cannot be determined
  3. Inspect the FetchVerse and FetchPassage functions
    Open the Bible ModuleScript and locate the FetchVerse and FetchPassage function definitions. Examine the code to see if input validation (such as sanitizing or validating the verse/passage parameters) is performed before constructing the API request URL.
    Affected if No input validation is present and the functions directly concatenate user input into URLs
  4. Check how API URLs are constructed
    Look for string concatenation or string.format operations that build the API request URL using the verse or passage parameters. Verify if parameters are passed through any validation, sanitization, or allowlist checks before being used in the URL.
    Affected if Parameters are directly interpolated into URLs without validation checks
  5. Verify if external API calls are made
    Search for HttpService or similar HTTP request calls within the module. Check if these calls use the verse/passage parameters in the request URL without proper safeguards.
    Affected if HTTP requests are made using unvalidated input from FetchVerse or FetchPassage parameters

A user is affected if they have the Bible Module installed with a version prior to 0.0.3 and the FetchVerse/FetchPassage functions do not validate or sanitize input before using it in API request URLs.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to version 0.0.3 which includes proper input validation. No workarounds are available.

Recommended fix High confidence

version 0.0.3

  1. Locate the Bible Module dependency in your ROBLOX project
  2. Update the Bible Module to version 0.0.3 or later
  3. Verify that the FetchVerse and FetchPassage functions now properly validate input before making API requests
  4. Test the updated module to confirm it handles malicious input correctly

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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