CVE-2025-10345
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 parameters 'name' and 'address' at the endpoint 'admin/leads/lead'.
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 confidenceStored HTML injection vulnerability in Perfex CRM v3.2.1 where the 'name' and 'address' parameters in the admin/leads/lead endpoint lack proper input validation, allowing malicious HTML/JavaScript to be stored and rendered when users view lead data.
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.
-
Check Perfex CRM installed versionLocate the version file or admin panel version display (typically in application/config/config.php, admin area footer, or system info page)Affected if Installed version is >= 3.2.1 and < 3.4.0
-
Verify Leads module is activeLog into the admin panel and navigate to Settings > Modules, or inspect the database table for active modulesAffected if Leads module is enabled and accessible to users
-
Inspect leads database for stored HTML/JavaScriptQuery the leads table (typically tblleads or similar) for the name and address fields, searching for patterns like <script, <img, javascript:, or other HTML tags in the dataAffected if Records contain unescaped HTML or JavaScript in name or address fields
-
Review lead creation/edit form validationSubmit a test lead with name=<script>alert(1)</script> and address=<img src=x onerror=alert(1)> to the admin/leads/lead endpoint, then view the lead to see if script executesAffected if The submitted HTML/JavaScript is rendered without encoding when the lead is viewed
User is affected if running Perfex CRM version 3.2.1 through 3.3.x with the Leads module enabled and no output encoding is applied to name/address fields.
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 using allowlist approaches on the 'name' and 'address' fields, and apply output encoding/HTML escaping when rendering lead data to prevent script execution.
Perfex CRM 3.4.0 or later
- Backup the Perfex CRM database and files before proceeding with any upgrade
- Download Perfex CRM version 3.4.0 or the latest stable release from the official vendor
- Follow the official Perfex CRM upgrade documentation to install the new version
- After upgrade, verify the fix by creating a test lead with potentially malicious input in the 'name' and 'address' fields at the admin/leads/lead endpoint
- Confirm that the input is properly sanitized and no HTML/JavaScript is executed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10345 — 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-10345 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