CVE-2025-54865
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 · uneditedTilesheets MediaWiki Extension adds a table lookup parser function for an item and returns the requested image. A missing backtick in a query executed by the Tilesheets extension allows users to insert and potentially execute malicious SQL code. This issue has not been fixed.
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 · moderate confidenceSQL injection vulnerability in the Tilesheets MediaWiki extension due to a missing backtick in a database query. The extension's table lookup parser function for item images fails to properly sanitize input, allowing attackers to inject malicious SQL code through the vulnerable query parameter.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.0.1, < 5.0.3CVSS 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.
-
Locate Tilesheets extension installationCheck for the Tilesheets extension directory in your MediaWiki installation (typically in /extensions/Tilesheets/ or similar). Look for the extension.json or SpecialTilesheets.php file to confirm installation.Affected if The Tilesheets extension directory exists and contains the extension files.
-
Determine installed Tilesheets versionOpen the extension.json file in the Tilesheets directory and read the 'version' field, or check the composer.json / version file if present. Compare the version number against the affected range: >= 5.0.1 and < 5.0.3.Affected if The installed version is 5.0.1, 5.0.2, or any version meeting version >= 5.0.1 AND version < 5.0.3.
-
Verify extension is enabled in MediaWikiCheck your LocalSettings.php file for a line enabling the extension, such as wfLoadExtension( 'Tilesheets' ) or require_once. Confirm the extension is actively loaded.Affected if The extension is enabled and loaded by MediaWiki at runtime.
-
Confirm user authentication is requiredCheck if your MediaWiki $wgGroupPermissions allow anonymous users to edit or use parser functions. Look at $wgGroupPermissions['*']['edit'] and related settings in LocalSettings.php.Affected if The vulnerability requires an authenticated user; if anonymous edits are allowed, the attack surface is different but still present.
-
Check if parser function is accessibleVerify the table lookup parser function is callable. Try using {{#tilesheet:...}} or the relevant parser function syntax on any wiki page to confirm the function is registered and operational.Affected if The parser function is registered and can be invoked by users.
You are affected if Tilesheets extension version is 5.0.1 or 5.0.2 (or any version >= 5.0.1 and < 5.0.3), the extension is enabled, and the table lookup parser function is accessible to authenticated users.
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.
dbcve · scoped5.0.3
As the vulnerability remains unfixed, immediately disable or remove the Tilesheets extension if possible. If the extension must remain in use, implement input validation and parameterized queries at the application layer, and consider deploying a WAF rule to block SQL injection patterns as a temporary protective measure until a patch is available.
Tilesheets extension version 5.0.3 or later
- 1. Backup your MediaWiki database and files before making any changes.
- 2. Identify your current Tilesheets extension version by checking the extension's version file or composer.json.
- 3. Upgrade the Tilesheets extension to version 5.0.3 or later.
- 4. If using Composer, run: composer require mediawiki/tilesheets:"^5.0.3" or composer update mediawiki/tilesheets.
- 5. Alternatively, download the updated extension from the MediaWiki Tilesheets repository.
- 6. Clear any MediaWiki cache after upgrading.
- 7. Verify the extension loads correctly and test the parser function functionality.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54865 — 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-54865 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