CVE-2026-25013
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WHMCSdes Phox Hosting phox-host allows Reflected XSS.This issue affects Phox Hosting: from n/a through <= 2.0.8.
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 confidenceReflected XSS vulnerability in Phox Hosting (WHMCS addon) allows attackers to inject malicious scripts via unsanitized user input that gets reflected back in web pages without proper encoding. The vulnerability affects versions through 2.0.8.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Verify Phox Hosting addon installationCheck the WHMCS admin panel under 'Addons' or 'Module Commands' for the presence of the Phox Hosting addon, or inspect the /modules/addons/ directory for a 'phox' or 'phoxhosting' folder.Affected if The Phox Hosting addon is present in the WHMCS installation.
-
Identify installed Phox Hosting versionLocate the version file or module configuration within the Phox Hosting addon directory (commonly in /modules/addons/phox/ or similar), or check the addon information in the WHMCS admin interface.Affected if The installed version is 2.0.8 or any earlier version (any version through 2.0.8 is affected).
-
Locate user input reflection pointsReview the PHP source files in the Phox Hosting addon for instances where $_GET, $_POST, or $_REQUEST parameters are directly output to HTML without using HTML encoding functions such as htmlspecialchars() or equivalent escaping methods.Affected if Any script or template file in the addon outputs request parameters directly into HTML output without sanitization.
-
Identify accessible web-facing entry pointsExamine the public-facing pages or hooks provided by the addon (typically accessible via /index.php?m=phox or similar WHMCS module URLs), and identify which user-supplied parameters are reflected in the response.Affected if The addon exposes parameters that accept user input and reflect that input back in the page response without encoding.
You are affected if the Phox Hosting addon is installed with version 2.0.8 or earlier and the addon processes and reflects user-supplied input in web pages without proper HTML encoding.
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 dataImplement proper input validation and output encoding/escaping for all user-supplied data before rendering in HTML contexts. Use context-appropriate sanitization functions and consider Content Security Policy headers.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25013 — 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-2026-25013 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