CVE-2025-10343
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 'expense_name' at the endpoint '/expenses/expense'.
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 confidenceA stored HTML injection vulnerability exists in Perfex CRM v3.2.1 where the 'expense_name' parameter in POST requests to /expenses/expense is not properly validated or sanitized before storage. This allows attackers to inject arbitrary HTML tags that render when other users view the expenses list, potentially enabling phishing or content manipulation 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 installed Perfex CRM versionLocate the version file or admin panel version display (typically in /application/config/config.php or Admin > Settings > Info). Compare the version number against the affected range: >= 3.2.1 and < 3.4.0.Affected if The installed version falls within 3.2.1 through 3.3.x (any version less than 3.4.0).
-
Confirm expenses module is enabledLog into the Perfex CRM admin panel and navigate to Admin > Settings > Modules (or check /modules/ directory). Verify that the Expenses module is installed and active.Affected if The Expenses module is enabled and accessible to users who can create expenses.
-
Verify user access to expense creationNavigate to Expenses > New Expense (or /expenses/expense endpoint). Check if the current user role has permission to create expenses via Admin > Staff > Roles or Admin > Customers > Customer Groups permissions.Affected if User accounts exist with permission to create or submit expenses.
-
Inspect expenses list for injected contentNavigate to Expenses > All Expenses (or view the expenses list). Examine the expense names displayed in the list for any unexpected HTML tags, scripts, or suspicious links that were not entered as plain text.Affected if The expenses list displays HTML tags, JavaScript, or unexpected formatting in expense name fields that were not intentionally entered.
You are affected if your Perfex CRM version is 3.2.1 through 3.3.x, the Expenses module is enabled, and users can create expenses without HTML sanitization being applied to the expense_name field.
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 HTML encoding for the expense_name parameter, ensuring all user-supplied content is sanitized before storage and properly escaped when rendered. Consider implementing a whitelist approach for allowed characters and using established sanitization libraries.
Perfex CRM 3.4.0 or later
- Backup your Perfex CRM database before proceeding with any upgrade
- Download Perfex CRM version 3.4.0 or later from the official vendor source
- Follow the standard Perfex CRM upgrade procedure to install the new version
- After upgrade, verify the fix by testing that HTML/script tags in the expense_name parameter at /expenses/expense are properly sanitized or blocked
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10343 — 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-10343 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