CVE-2025-10346
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 'subject' at the endpoint 'knoewledge_base/article'.
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 attackers to inject malicious HTML/script content via the 'subject' parameter when creating knowledge base articles at the knowledge_base/article endpoint. The injected payload is stored and rendered when other users view the article, potentially leading to session hijacking or phishing attacks.
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 and determine the version number, typically found in the admin dashboard under Settings > Info or in a version.php file in the application directoryAffected if The software is Perfex CRM and the version falls between 3.2.1 and 3.3.9 inclusive (any version >= 3.2.1 but < 3.4.0)
-
Verify knowledge base module is accessibleConfirm the knowledge base feature is enabled and accessible by navigating to the knowledge_base/article endpoint or checking if staff/users can create knowledge base articlesAffected if The knowledge base module is enabled and users have permission to create articles
-
Check for existing malicious articlesQuery the database for knowledge base articles with suspicious HTML/script content in the subject field. Example SQL: SELECT * FROM tblknowledgebasearticles WHERE subject LIKE '%<script%' OR subject LIKE '%<img%' OR subject LIKE '%onerror%' OR subject LIKE '%javascript:%'Affected if Any knowledge base article records contain unsanitized HTML or script tags in the subject field
-
Inspect HTTP response for XSS vulnerabilitiesCreate a test knowledge base article with a benign payload like <img src=x onerror=alert(1)> in the subject field, save it, then view the article and inspect the page source to see if the payload is rendered as-is without encodingAffected if The subject parameter content is rendered without HTML encoding when viewing the article
A user is affected if running Perfex CRM version 3.2.1 through 3.3.x with the knowledge base module enabled and the subject parameter allows unsanitized HTML to be stored and displayed to other users.
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 proper input validation and output encoding for the 'subject' parameter - sanitize or reject HTML/script tags on input and encode output when displaying knowledge base article subjects.
Perfex CRM 3.4.0 or later
- Create a complete backup of the Perfex CRM database and all files
- Download Perfex CRM version 3.4.0 or later from the official vendor source
- Review the official upgrade documentation for Perfex CRM
- Upload the new version files, ensuring to preserve custom configurations
- Run the database migration scripts included with the upgrade
- Verify that the knowledge_base/article endpoint now properly validates the 'subject' parameter
- Test that HTML/script tags are properly escaped when submitted in the subject field
- Confirm all other CRM functionality operates normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10346 — 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-10346 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