Security readout for executives and security teams
Plain-English summary
GigToDo Freelance Marketplace Script 1.3 can store attacker-supplied script content in proposal descriptions. If an administrator or user views the proposal, browser-side code may run in that viewer's session. The main business risk is account compromise, data exposure, or malicious redirection inside a marketplace deployment.
Executive priority
Treat as a moderate web application risk. Prioritize if GigToDo handles sensitive user data, payments, or administrator workflows, because successful exploitation can target privileged sessions through normal proposal review activity.
Technical view
CVE-2019-25739 is stored XSS in the proposal description field of GigToDo 1.3. Authenticated attackers can submit malicious HTML or JavaScript through create_proposal, later executing when another user views the stored proposal. CVSS 3.1 is 5.4, requiring low privileges and user interaction, with changed scope and low confidentiality/integrity impact.
Likely exposure
Exposure is most likely where GigToDo 1.3 is deployed and authenticated users can create proposals reviewed by administrators or other users. The source bundle does not provide reliable CPE data or a fixed-version range.
Exploitation context
A public ExploitDB reference exists, so technical details were publicly disclosed. The bundle does not show CISA KEV listing or any cited evidence of active exploitation in the wild.
Researcher notes
Evidence identifies stored XSS through proposal descriptions in GigToDo 1.3. The affected metadata is incomplete, listing GigToDo with version 0 and no CPEs. No source in the bundle names a patch, fixed release, or active exploitation.
Mitigation direction
- Check GigToDo vendor guidance for a fixed version or official workaround.
- Restrict proposal creation to trusted authenticated users until remediated.
- Ensure proposal descriptions are server-side sanitized and output-encoded before display.
- Review and remove stored proposal content containing unexpected script or HTML.
- Invalidate affected sessions if suspicious stored content is found.
Validation and detection
- Inventory deployed GigToDo instances and confirm whether version 1.3 is present.
- Review create_proposal handling for proposal description validation and encoding.
- Check proposal records for unexpected script tags, event handlers, or redirect markup.
- Confirm stored proposal text renders as inert text in admin and user views.
- Review access logs for suspicious proposal submissions followed by privileged views.
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.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-25739 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
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
5.1MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-47185CVE reference, VulnCheck · exploit
- Official Product HomepageCVE reference, VulnCheck · product
- Product ReferenceCVE reference, VulnCheck · product
- VulnCheck Advisory: GigToDo Freelance Marketplace Script 1.3 Persistent XSSCVE reference, VulnCheck · third-party-advisory
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.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.