CVE-2025-10341
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 · uneditedHTML injection vulnerability in Perfex CRM v3.2.1 consisting of a stored HTML injection due to lack of proper validation of user input by sending a POST request in the parameter 'company' at the endpoint '/clients/client/x.
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 confidenceStored HTML injection vulnerability in Perfex CRM v3.2.1 allows authenticated users to inject arbitrary HTML code via the 'company' parameter in POST requests to the /clients/client/x endpoint due to lack of proper input validation and sanitization.
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>= 3.2.1, < 3.4.0CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Identify Perfex CRM installationLocate the Perfex CRM installation directory on the server. Check for the presence ofPerfex CRM files, typically in the web root. Look for the main index.php or admin.php files, and check the application/config/config.php for system markers.Affected if Perfex CRM software is present on the server
-
Determine installed versionCheck the Perfex CRM version by examining the /application/config/config.php file for the 'app_version' constant, or look for a version.php file in the application folder, or check the footer of the admin panel login page.Affected if Installed version is 3.2.1 or higher but below 3.4.0
-
Verify client portal is accessibleConfirm that the client portal endpoint /clients/ is accessible and functional on the web server. This is required for the vulnerable endpoint to be reachable.Affected if The client portal module is enabled and accessible at /clients/
-
Confirm user authentication is enabledVerify that user registration or client account creation is enabled in Perfex CRM settings. Check Admin > Settings > Customers > Allow customers to register is turned on, or confirm client accounts exist in the database.Affected if Authenticated user accounts can access the client portal
The environment is affected if Perfex CRM version is 3.2.1 or higher but below 3.4.0, the client portal is accessible, and user authentication is enabled allowing access to the /clients/client/x endpoint.
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 · scoped3.4.0
Implement strict input validation and output encoding for the 'company' parameter; sanitize or reject HTML/script tags at the server-side before storage and encode output when rendering.
3.4.0
- Upgrade Perfex CRM to version 3.4.0 or later to resolve the stored HTML injection vulnerability in the 'company' parameter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10341 — 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-10341 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