dbcve.org
Perfex CrmApplication · Perfexcrm

CVE-2025-10342

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-29
Fix available
A fix is available. Upgrade to 3.4.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
HTML 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 'name' at the endpoint '/subscriptions/create'.

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 confidence

Stored HTML injection vulnerability in Perfex CRM v3.2.1 allows attackers to inject malicious HTML code through the 'name' parameter at the /subscriptions/create endpoint. Due to lack of proper input validation, the injected HTML is stored in the database and rendered when other users view the subscription data, enabling potential session hijacking, phishing, or defacement.

MitigationImplement strict input validation and sanitization for the 'name' parameter, combined with proper output encoding when rendering subscription data to prevent HTML/JavaScript execution.

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
Perfex CrmApplication
Affected:>= 3.2.1, < 3.4.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Perfex CRM installed version
    Locate the version file in your Perfex CRM installation (typically version.php in the root or application/config/ directory) or check the admin dashboard footer for the version number
    Affected if Installed version is 3.2.1 or higher but lower than 3.4.0
  2. Verify subscriptions module is enabled
    Log into the admin panel and navigate to Settings > Modules > Subscriptions to confirm the subscriptions module is active, or check the database table tblmodules for the subscriptions entry where active=1
    Affected if Subscriptions module is enabled and accessible
  3. Confirm /subscriptions/create endpoint exists
    Attempt to access /subscriptions/create or check your web server logs for requests to this endpoint, or inspect the subscriptions controller file in application/controllers/Subscriptions.php
    Affected if The subscriptions create functionality is present in the application
  4. Inspect subscription database records for malicious content
    Query the tblsubscriptions table in your database and examine the 'name' column for any unexpected HTML tags (such as <script>, <iframe>, <img>, or javascript: URIs) that may indicate stored XSS payloads
    Affected if Any records in tblsubscriptions contain raw HTML or JavaScript in the name field that is not properly escaped

You are affected if your Perfex CRM version is 3.2.1 or higher but below 3.4.0, the subscriptions module is enabled, and unescaped HTML/JavaScript exists in subscription name fields in the database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.4.0 or later
Fixed in 3.4.0
Interim mitigation

Implement strict input validation and sanitization for the 'name' parameter, combined with proper output encoding when rendering subscription data to prevent HTML/JavaScript execution.

Recommended fix Moderate confidence

Perfex CRM 3.4.0 or later

  1. 1. Create a complete backup of the Perfex CRM database and all application files
  2. 2. Download Perfex CRM version 3.4.0 or later from the official vendor website
  3. 3. Review the official upgrade documentation for version 3.4.0
  4. 4. Upload the new version files to your server, overwriting the existing installation
  5. 5. Run any database migration scripts included in the upgrade package
  6. 6. Clear all application caches after the upgrade
  7. 7. Log in to the CRM and navigate to the /subscriptions/create endpoint
  8. 8. Test that the 'name' parameter now properly sanitizes HTML/script input
Caveat Minor version upgrades may include database schema changes and feature modifications - review changelog before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Perfex Crm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10342 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10342 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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