CVE-2025-66022
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 · uneditedFACTION is a PenTesting Report Generation and Collaboration Framework. Prior to version 1.7.1, an extension execution path in Faction’s extension framework permits untrusted extension code to execute arbitrary system commands on the server when a lifecycle hook is invoked, resulting in remote code execution (RCE) on the host running Faction. Due to a missing authentication check on the /portal/AppStoreDashboard endpoint, an attacker can access the extension management UI and upload a malicious extension without any authentication, making this vulnerability exploitable by unauthenticated users. This issue has been patched in version 1.7.1.
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 confidenceFaction versions before 1.7.1 contain a critical authentication bypass vulnerability where the /portal/AppStoreDashboard endpoint lacks authentication checks, allowing unauthenticated attackers to access the extension management UI and upload malicious extensions that execute arbitrary system commands (RCE) on the host server.
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< 1.7.1CVSS 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.
-
Determine installed Faction versionLocate the Faction installation directory and check the version file, or run 'faction --version' if CLI is available, or check the application banner on startupAffected if The version is lower than 1.7.1 (e.g., 1.7.0, 1.6.x, etc.)
-
Verify if /portal/AppStoreDashboard endpoint is exposedSend an HTTP GET request to http(s)://<your-faction-server>/portal/AppStoreDashboard without providing any authentication headers or tokensAffected if The endpoint returns a 200 OK response with the extension management UI instead of requiring authentication (401/403)
-
Check for unauthorized extension uploadsInspect the Faction extensions directory (typically found in the application data folder under /extensions or /uploads) for any unexpected .faction or .zip extension files that were not uploaded by legitimate administratorsAffected if New or unknown extension files exist in the extensions directory that were not uploaded by authorized users
-
Review access logs for the vulnerable endpointExamine Faction server access logs (usually in /logs or the application data directory) for GET or POST requests to /portal/AppStoreDashboard from unexpected IP addresses, particularly without corresponding authentication log entriesAffected if Requests to /portal/AppStoreDashboard appear in logs from unknown IP addresses without prior authentication
You are affected if your Faction version is below 1.7.1 and the /portal/AppStoreDashboard endpoint is accessible without authentication, or if evidence of unauthorized extension uploads exists in your system.
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 · scoped1.7.1
Upgrade Faction to version 1.7.1 or later immediately to remediate this vulnerability. Additionally, review server logs and systems for indicators of compromise given the RCE capability and potential unauthorized access prior to patching.
1.7.1
- Upgrade Faction to version 1.7.1 or later to apply the security patch that adds authentication checks to the /portal/AppStoreDashboard endpoint
- Verify the patch was applied by confirming the authentication check is now in place on the extension management endpoint
- After upgrading, review any uploaded extensions to ensure no malicious extensions were added prior to the fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66022 — 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-66022 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