CVE-2025-47667
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in qusupport LiveAgent liveagent allows Cross Site Request Forgery.This issue affects LiveAgent: from n/a through <= 4.4.7.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in qusupport LiveAgent allows attackers to trick authenticated users into performing unintended actions. The vulnerability exists in LiveAgent versions through 4.4.7, where proper CSRF token validation or SameSite cookie attributes are likely missing for state-changing requests.
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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Determine installed LiveAgent versionLocate the version information in the application admin panel, footer of the web interface, or configuration files (commonly found in /config/version.php, /include/version.php, or similar paths under the web root)Affected if The installed version number is 4.4.7 or lower
-
Inspect session cookies for SameSite attributeLog into LiveAgent, open browser developer tools (F12), go to Application > Cookies, and examine all cookies with names like PHPSESSID, session, or similar session identifiers. Check the SameSite column for each cookieAffected if No session cookies have the SameSite attribute set, or the SameSite value is empty or missing
-
Verify CSRF token presence on state-changing requestsLog in to LiveAgent and attempt a state-changing action (such as creating, editing, or deleting a ticket, changing user settings, or modifying configuration). Use browser developer tools to capture the HTTP request and inspect whether a CSRF token parameter or header is included in the requestAffected if State-changing requests do not include a CSRF token parameter (such as csrf_token, token, or _token) or custom header
-
Test Origin header validation on sensitive endpointsSend a manual HTTP request to a sensitive LiveAgent endpoint (such as ticket creation or user modification) with an arbitrary Origin header (e.g., Origin: http://malicious-site.com) using a tool like curl or Burp Suite, and observe whether the request is accepted or rejectedAffected if The request is processed without returning an error or being blocked based on the Origin header value
Your environment is affected if you are running LiveAgent version 4.4.7 or lower AND your session cookies lack SameSite attributes OR your state-changing endpoints do not require CSRF tokens.
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 anti-CSRF tokens for all state-changing operations and configure SameSite attributes on session cookies. Verify the Origin/Referer headers are validated on sensitive requests.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47667 — 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-47667 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