Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #43357 Missing CSRF protection on tracker reports manipulation
    Infos
    #43357
    Thomas Gerbet (tgerbet)
    2025-06-25 09:50
    2025-06-11 17:15
    45067
    Details
    Missing CSRF protection on tracker reports manipulation

    There is no CSRF protection when creating, updating or deleting a tracker report.

    Impact

    An attacker could use this vulnerability to trick victims into creating/removing/updating tracker reports.
    CVSSv3.1 score: 4.6 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L)

    References

    CWE 352
    Cross-Site Request Forgery - OWASP
    CVE-2025-50179

    Trackers
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Thomas Gerbet (tgerbet)
    Closed
    2025-06-13
    Attachments
    Empty
    References
    Referencing request #43357

    Git commit

    tuleap/tuleap/stable

    fix: request #43357 Missing CSRF protection on tracker reports manipulation 8e0e7a20fc
    User avatar Thomas Gerbet (tgerbet) , 2025-06-13 16:02
    Merge commit 'refs/changes/82/34682/5' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 0f9aab6e36
    User avatar Joris MASSON (jmasson) , 2025-06-13 17:58
    fix: Cannot add/modify a tracker report renderer a40a53035d
    User avatar Thomas Gerbet (tgerbet) , 2025-06-18 10:56
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2025-06-18 09:26

    CVE-2025-50179 has been assigned to this issue.

    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes