Security readout for executives and security teams
Plain-English summary
This issue affects the Drupal amoCRM module before 7.x-1.2. A remote attacker could submit crafted POST data that causes script or HTML to run in a user’s browser. Business risk depends on whether the module is installed and who can trigger or view the affected workflow.
Executive priority
Treat this as a targeted remediation item for legacy Drupal environments. It is not shown as actively exploited in the provided sources, but XSS in business integrations can expose sessions, data, or admin actions if the vulnerable workflow is reachable.
Technical view
CVE-2015-7304 is a cross-site scripting vulnerability in amoCRM module 7.x-1.x before 7.x-1.2 for Drupal. The public description says the input vector is unspecified HTTP POST data. No CVSS, CWE, affected CPE, or detailed attack preconditions are provided in the bundle.
Likely exposure
Exposure is likely limited to Drupal 7 sites running the amoCRM module 7.x-1.x before version 7.x-1.2. Sites not using this module are not indicated as affected by the provided sources.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. The sources describe remote injection of script or HTML, but do not provide exploit maturity, authentication requirements, or affected form details.
Researcher notes
Evidence is thin: the source bundle names XSS via unspecified HTTP POST data but lacks CVSS, CWE, CPEs, affected endpoint details, and exploit status. Validation should focus on version confirmation and advisory review, not assumed exploitability beyond the published description.
Mitigation direction
- Inventory Drupal sites for the amoCRM module and installed version.
- Upgrade the amoCRM module to 7.x-1.2 or later where applicable.
- Check Drupal advisory pages for vendor-specific update guidance.
- Prioritize sites where privileged users interact with amoCRM workflows.
- Review logs for unusual POST activity around affected module paths.
Validation and detection
- Confirm whether each Drupal 7 site has the amoCRM module enabled.
- Verify the installed module version is 7.x-1.2 or later.
- Review the Drupal advisory references for local applicability.
- Confirm no untrusted HTML or script renders in amoCRM-related workflows.
- Document compensating controls if immediate upgrade is not possible.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2015-7304 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.drupal.org/node/2569587CVE reference · x_refsource_MISC
- https://www.drupal.org/node/2569243CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.