Skip to main content
Menu
CVEs

WeGIA missing authentication in atualiza_pagamentos.php

Affects WeGIA 3.8.6 and earlier, where the atualiza_pagamentos.php endpoint does not check whether the requester is authenticated. Fixed in 3.8.7.

CVE-2026-61675EUVD-2026-128187Published November 17, 2026, updated

9.8CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 3.8.7
Who is exposed
Not reported

Summary

Written by a model

WeGIA is a web manager for charitable institutions. Prior to 3.8.7, web/html/socio/sistema/atualiza_pagamentos.php performs payment-status database updates without checking whether the requester has an authenticated session. An unauthenticated remote requester can supply a payment identifier, payment date, and paid value to mark arbitrary payment records as paid or otherwise modify payment information, causing financial record corruption. This issue is fixed in version 3.8.7.

Who should check

Teams running WeGIA 3.8.6 or earlier, the charity management web app, including its socio (member) payment pages.

“The endpoint web/html/socio/sistema/atualiza_pagamentos.php performs payment status updates without verifying whether the requester is authenticated.”

github.com

What to do

Upgrade to a fixed version: 3.8.7.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-61675 (WeGIA: Missing Authentication in atualiza_pagamentos.php Allows Unauthorized Payment Manipulation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-61675 (entry last updated 2026-11-18):
Affected:
- LabRedesCefetRJ WeGIA: fixed in 3.8.7
Fixed versions: 3.8.7.
Conditions (all must be true for the bug to be hit):
- The endpoint atualiza_pagamentos.php in WeGIA 3.8.6 or earlier does not verify that the requester is authenticated. (source: https://github.com/LabRedesCefetRJ/WeGIA/security/advisories/GHSA-c6vj-372g-m3cw)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-61675 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-61675 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/LabRedesCefetRJ/WeGIA/security/advisories/GHSA-c6vj-372g-m3cw
- https://github.com/LabRedesCefetRJ/WeGIA/pull/1705
- https://github.com/LabRedesCefetRJ/WeGIA/commit/a820c2fed9180945753e25fe93e927c764f8f650
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-61675
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-61675"}.

Affected versions

cve.now Index

45of 100 · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 50 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now1 day
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: total

  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 17Nov 22
  • EPSS: 0.59%
  • Posted on X by cve.now Nov 18

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · LabRedesCefetRJ/WeGIA · Advisory GHSA-c6vj-372g-m3cw
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-61675
RecordNVD · CVE-2026-61675
Other links 2
RepositoryGitHub · LabRedesCefetRJ/WeGIA · Pull request #1705
RepositoryGitHub · LabRedesCefetRJ/WeGIA · Commit a820c2fe

Questions about CVE-2026-61675

Is CVE-2026-61675 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The atualiza_pagamentos.php endpoint updates payment status without verifying that the requester is authenticated. Arbitrary payment records can be marked as paid, payment information can be modified, and financial records can be corrupted.

Source: github.com

Which versions are affected by CVE-2026-61675?

WeGIA: before 3.8.7.

Source: cve.now feed data

Am I affected, and how do I check?

WeGIA 3.8.6 and earlier are affected, through the endpoint web/html/socio/sistema/atualiza_pagamentos.php. To check, compare the installed WeGIA version with 3.8.6.

Source: github.com

How do I fix CVE-2026-61675?

Upgrade WeGIA to 3.8.7, the fixed version.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.