other
- Location
scripts/update_linkedin.py:69- Finding
Odoo Contact PII Disclosed to an External Search Provider
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it says, but it automatically sends contact details to DuckDuckGo and writes an unverified search result into Odoo CRM records.
Install only if you are comfortable letting the skill use your Odoo credentials to update contact records and send each selected contact's name and company to DuckDuckGo. Review the found LinkedIn URL before saving it, and avoid using this unchanged in environments with strict CRM data integrity, privacy, or third-party processing requirements.
scripts/update_linkedin.py:69Odoo Contact PII Disclosed to an External Search Provider
scripts/update_linkedin.py:14Insufficient Validation of Search-Derived URL Before Odoo Write
The skill advertises and relies on environment-variable access and outbound network access, but it does not declare any explicit tool scope or permissions boundary. That makes the capability set implicit rather than reviewable, increasing the chance of over-privileged execution or unexpected secret/network use when the skill is invoked.
The skill updates res_partner.x_linkedin_url in Odoo, but the description does not prominently warn that it will modify CRM data. Users may invoke it expecting a lookup-only action, leading to unintended writes, bad profile matches, or silent data integrity issues in business records.
The script builds a search query from an Odoo contact's name and company and sends it to DuckDuckGo, which discloses personal/business contact data to a third-party service without explicit consent, notice, or approval controls. In this skill's context, that external transmission is core behavior, so the privacy risk is real and not merely theoretical, especially in regulated or confidentiality-sensitive environments.