Web To Sugarcrm Lead
Approved changes feed: RSS · Atom
cpe:2.3:a:dipesh_patel:web_to_sugarcrm_lead:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Dipesh Patel (cb9df0fe-d76d-5dcc-8a34-4dffeb0e12dc) |
|---|---|
| Product | Web To Sugarcrm Lead (44139a5f-7a7c-5750-b42c-d6362897ed3a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-13361 |
vulnerable | 2026-06-08 07:04:32.058187 |
Web to SugarCRM Lead <= 1.0.0 - Cross-Site Request Forgery to Custom Field Deletion
MEDIUM (4.3)
The Web to SugarCRM Lead plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.0. This is due to missing nonce validation on the custom field deletion functionality. This makes it possible for unauthenticated attackers to delete custom fields via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Published: 2025-12-21T03:20:06.716Z
Updated: 2026-04-08T17:17:41.914Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.