CVE-2025-48732
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 · uneditedAn incomplete blacklist exists in the .htaccess sample of WWBN AVideo 14.4 and dev master commit 8a8954ff. A specially crafted HTTP request can lead to a arbitrary code execution. An attacker can request a .phar file to trigger 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 confidenceThe .htaccess sample file in WWBN AVideo contains an incomplete blacklist that fails to properly block or safely handle .phar (PHP archive) files. When an attacker requests a .phar file directly, the server may execute the embedded PHP code within the archive, allowing arbitrary code execution.
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= 14.4CVSS 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 the .htaccess file in the AVideo installationFind the .htaccess file in the web root directory of the WWBN AVideo installation. Common locations include the root directory where index.php resides.Affected if The .htaccess file exists but does not contain a rule to deny access to .phar files.
-
Check if .phar is explicitly denied in .htaccessOpen the .htaccess file and search for 'phar' or '.phar' entries. Look for rules like 'deny from all', 'RewriteRule.*\.phar$', or similar blacklist entries.Affected if There is no RewriteRule or FilesMatch directive blocking or denying access to .phar file extensions.
-
Verify the installed AVideo versionCheck the version file or admin panel in AVideo to confirm the exact version number installed.Affected if The installed version is exactly 14.4.
-
Test for .phar file execution capabilityAttempt to access a known .phar file via HTTP request (e.g., http://yourserver/anyfile.phar) or check if .phar files exist in publicly accessible directories.Affected if The server returns a 200 OK response or executes the .phar file instead of returning a 403 Forbidden or 404 Not Found.
A user is affected if they are running Wwbn AVideo version 14.4 and the .htaccess file lacks rules to block or deny direct access to .phar files.
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 .htaccess file with a complete blacklist to deny direct access to .phar files, or configure the server to treat .phar files as non-executable (e.g., by serving them with Content-Type: application/octet-stream or blocking .phar access entirely).
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48732 — 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-48732 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