[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3xYVqa89N2AhNwM6Sx8eY18k9zUV6c1UbZpWEbLN0mY":3,"g5a-risk:CVE-2026-53644":90},{"success":4,"data":5,"meta":87},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":29,"epssPercentile":30,"epssTimeSeries":31,"severity":32,"affectedProducts":33,"affectedProductsCount":34,"references":35,"referencesCount":40,"weaknesses":41,"weaknessesCount":40,"isActivelyExploited":50,"cisaInfo":30,"otxData":30,"relatedBlogPosts":51,"seoMetadata":52,"configurations":77,"relatedVendorCves":78,"notableEvents":79},"CVE-2026-53644","What is CVE-2026-53644?","FOSSBilling is a free, open-source billing and client management system. Versions 0.5.3 through 0.7.2 allow authenticated clients to both read and reset API key service secrets for orders that are no longer in an `active` state (e.g., `suspended`, `canceled`). The root cause is missing order-state validation in two client API endpoints, despite an `isActive()` helper already existing in the `Serviceapikey` module and the frontend UI correctly gating access on `order.status == 'active'`. Version 0.8.0 contains a fix. Some workarounds are available. If the `Serviceapikey` module is not needed, uninstall it to remove the affected endpoints. One may also use a reverse proxy or WAF to restrict access to `\u002Fapi\u002Fclient\u002Forder\u002Fservice` and `\u002Fapi\u002Fclient\u002Fserviceapikey\u002Freset` based on application-level order-state logic.","FOSSBilling is a free, open-source billing and client management system. Versions 0.5.3 through 0.7.2 allow authenticated clients to both read and reset API ...","2026-07-06T23:16:56.36","2026-07-07T14:16:32.743",8.6,"CVSS:4.0\u002FAV:N\u002FAC:L\u002FAT:N\u002FPR:L\u002FUI:N\u002FVC:H\u002FVI:H\u002FVA:N\u002FSC:N\u002FSI:N\u002FSA:N\u002FE:X\u002FCR:X\u002FIR:X\u002FAR:X\u002FMAV:X\u002FMAC:X\u002FMAT:X\u002FMPR:X\u002FMUI:X\u002FMVC:X\u002FMVI:X\u002FMVA:X\u002FMSC:X\u002FMSI:X\u002FMSA:X\u002FS:X\u002FAU:X\u002FR:X\u002FV:X\u002FRE:X\u002FU:X",{"CVSSMetricV31":15,"CVSSMetricV30":16,"CVSSMetricV2":17,"CVSSMetricV40":18},[],[],[],[19],{"Source":20,"Type":21,"CVSSData":22},"security-advisories@github.com","Secondary",{"Version":23,"VectorString":13,"BaseScore":12,"BaseSeverity":24,"AttackVector":25,"AttackComplexity":26,"AttackRequirements":27,"PrivilegesRequired":26,"UserInteraction":27,"VulnConfidentialityImpact":24,"VulnIntegrityImpact":24,"VulnAvailabilityImpact":27,"SubConfidentialityImpact":27,"SubIntegrityImpact":27,"SubAvailabilityImpact":27,"ExploitMaturity":28,"ConfidentialityRequirement":28,"IntegrityRequirement":28,"AvailabilityRequirement":28,"ModifiedAttackVector":28,"ModifiedAttackComplexity":28,"ModifiedAttackRequirements":28,"ModifiedPrivilegesRequired":28,"ModifiedUserInteraction":28,"ModifiedVulnConfidentialityImpact":28,"ModifiedVulnIntegrityImpact":28,"ModifiedVulnAvailabilityImpact":28,"ModifiedSubConfidentialityImpact":28,"ModifiedSubIntegrityImpact":28,"ModifiedSubAvailabilityImpact":28,"Safety":28,"Automatable":28,"Recovery":28,"ValueDensity":28,"VulnerabilityResponseEffort":28,"ProviderUrgency":28},"4.0","HIGH","NETWORK","LOW","NONE","NOT_DEFINED",0.00389,null,[29,29,29,29,29,29,29],"High",[],0,[36],{"url":37,"source":38,"tags":39},"https:\u002F\u002Fgithub.com\u002FFOSSBilling\u002FFOSSBilling\u002Fsecurity\u002Fadvisories\u002FGHSA-qf6j-vq68-qmfh","GitHub",[],1,[42],{"id":43,"name":44,"description":45,"extendedDescription":46,"status":47,"abstraction":48,"structure":49},"CWE-639","Authorization Bypass Through User-Controlled Key","The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.","Retrieval of a user record occurs in the system based on some key value that is under user control. The key would typically identify a user-related record stored in the system and would be used to lookup that record for presentation to the user. It is likely that an attacker would have to be an authenticated user in the system. However, the authorization process would not properly check the data access operation to ensure that the authenticated user performing the operation has sufficient entitlements to perform the requested data access, hence bypassing any other authorization checks present in the system.\nFor example, attackers can look at places where user specific data is retrieved (e.g. search screens) and determine whether the key for the item being looked up is controllable externally. The key may be a hidden field in the HTML form field, might be passed as a URL parameter or as an unencrypted cookie variable, then in each of these cases it will be possible to tamper with the key value.\nOne manifestation of this weakness is when a system uses sequential or otherwise easily-guessable session IDs that would allow one user to easily switch to another user's session and read\u002Fmodify their data.","Incomplete","Base","Simple",false,[],{"title":53,"metaDescription":54,"keywords":55,"canonicalUrl":56,"structuredData":57},"What is CVE-2026-53644? Vulnerability Analysis | Security Advisory | EdgeProtect","Comprehensive analysis of CVE-2026-53644, a high severity cyber security vulnerability from 2026. FOSSBilling is a free, open-source billing and client manag...","CVE-2026-53644, CVE-2026-53644 vulnerability, CVE-2026-53644 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2026, CVSS score, exploit, patch, remediation","\u002Fwhat-is\u002Fcve-2026-53644",{"@context":58,"@type":59,"headline":53,"description":54,"datePublished":10,"dateModified":11,"author":60,"publisher":64,"about":68,"mainEntityOfPage":72,"articleSection":75,"keywords":76},"https:\u002F\u002Fschema.org","TechArticle",{"@type":61,"name":62,"url":63},"Organization","EdgeProtect","https:\u002F\u002Fedgeprotect.io",{"@type":61,"name":62,"url":63,"logo":65},{"@type":66,"url":67},"ImageObject","https:\u002F\u002Fedgeprotect.io\u002Fimg\u002Flogos\u002Fedgeprotect-logo-512.png",{"@type":69,"name":6,"description":70,"additionalType":71},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":73,"@id":74},"WebPage","https:\u002F\u002Fedgeprotect.io\u002Fwhat-is\u002Fcve-2026-53644","Cybersecurity","CVE-2026-53644, CVE-2026-53644 vulnerability, CVE-2026-53644 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[],[],[80],{"id":81,"eventType":82,"eventTime":83,"details":84,"label":85,"color":86},"0deb85f2-efc5-4495-a38a-1abf6b969dd8","NEW_NVD","2026-07-07T04:01:18.50557+00:00","New CVE added to NVD","Published to NVD","blue",{"lastModified":11,"cacheTime":88,"version":89},1793195661934,"2.0",{"score":91,"band":92,"action":93,"scoredAt":94},48,"Medium","Plan remediation","2026-10-28T07:16:54.117424+00:00"]