Security readout for executives and security teams
Plain-English summary
Akaunting 2.1.12 and earlier could let someone who knows a user’s email address manipulate password reset flow through a live Akaunting instance. The issue was fixed in 2.1.13. Business risk is targeted account compromise or trust damage around password resets, not broad system takeover based on the supplied evidence.
Executive priority
Schedule remediation in the next normal security maintenance window for Akaunting systems, faster for internet-facing or multi-tenant deployments. The issue is medium severity but directly touches account recovery, a high-trust business workflow.
Technical view
The CVE describes password reset spoofing tied to Laravel default proxy-header handling in multi-tenant implementations. An unauthenticated network attacker with a target email can proxy reset requests through Akaunting. CVSS 3.1 is 5.4, with low confidentiality and integrity impact, no availability impact, and user interaction required.
Likely exposure
Highest exposure is public Akaunting deployments running 2.1.12 or earlier, especially behind proxies or in multi-tenant setups. Similar Laravel multi-tenant applications may be susceptible to comparable host/proxy-header reset-link issues, but this CVE’s named affected product is Akaunting.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The described attack requires knowing the target email address and user interaction. Treat it as a realistic targeted account-security issue, not proven mass exploitation.
Researcher notes
Evidence is limited to the CVE description and listed references. Do not expand the affected set beyond Akaunting without separate validation. The Laravel note is contextual: default behavior can enable similar patterns, but this CVE is not listed as a Laravel vulnerability.
Mitigation direction
- Upgrade Akaunting to version 2.1.13 or later.
- Check Akaunting vendor guidance for any additional remediation notes.
- Review trusted proxy and host-header handling in Laravel deployments.
- Verify password reset links are generated with the expected application host.
- Assess similar Laravel multi-tenant applications for host injection exposure.
Validation and detection
- Inventory all Akaunting deployments and record exact versions.
- Confirm no internet-facing instance runs 2.1.12 or earlier.
- Review password reset configuration for trusted host and proxy assumptions.
- Check application logs for unusual password reset activity.
- Validate related Laravel multi-tenant applications with host-injection checks.
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-640: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-36804 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:N/UI:R/S:U/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.
CVSS vector scores
1 official scoreWe 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:N/UI:R/S:U/C:L/I:L/A:N2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.rapid7.com/blog/post/2021/07/27/multiple-open-source-web-app-vulnerabilities-fixed/CVE reference · x_refsource_MISC
- https://www.laravel-enlightn.com/docs/security/host-injection-analyzer.htmlCVE reference · x_refsource_MISC
- https://github.com/laravel/laravel/pull/5477CVE reference · x_refsource_MISC
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.
Weak Password Recovery Mechanism for Forgotten Password
Weak Password Recovery Mechanism for Forgotten Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.