VulnerabilityPublished 22 Jun 2025Updated 23 Jun 2025

CVE-2025-6478: CodeAstro Expense Management System · Cross-Site Request Forgery

Affects CodeAstro Expense Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: Unreported

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: Unreported: Based on threat intelligence sources each of the following must apply: · No knowledge of publicly available proof-of-concept · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
CodeAstro Expense Management System	Affected =1.0	Fixed in–

AI-suggested

1. Implement CSRF tokens: Ensure that all state-changing requests in the CodeAstro Expense Management System require a unique, unpredictable CSRF token that is validated server-side. 2. Enforce SameSite cookie attributes: Configure session cookies with the 'SameSite' attribute set to 'Strict' or 'Lax' to reduce the risk of cross-origin requests. 3. User education: Train employees to recognize phishing attempts and suspicious links that could trigger CSRF attacks, emphasizing caution with unsolicited emails. 4. Monitor and audit: Enable detailed logging and regular audits of expense submissions and modifications to detect unusual patterns indicative of CSRF exploitation. 5. Network segmentation: Restrict access to the expense management system to trusted networks and VPNs to limit exposure. 6. Update and patch management: Engage with CodeAstro for patches or updates addressing this vulnerability and apply them promptly once available. 7. Multi-factor authentication (MFA): Although not directly preventing CSRF, MFA can reduce the risk of compromised credentials being used in conjunction with CSRF attacks. 8. Web Application Firewall (WAF): Deploy a WAF with rules to detect and block CSRF attack patterns and suspicious HTTP requests targeting the expense management system.

Description

A vulnerability was found in CodeAstro Expense Management System 1.0. It has been rated as problematic. Affected by this issue is some unknown functionality. The manipulation leads to cross-site request forgery. The attack may be launched remotely.

Impact

For European organizations using CodeAstro Expense Management System 1.0, this vulnerability poses a risk primarily to the integrity of financial data and transaction records. Unauthorized manipulation of expense entries could result in financial losses, compliance violations, and reputational damage. Since the system is likely used by finance departments, attackers exploiting this vulnerability could submit or alter expense claims without detection if proper auditing is not in place. The requirement for user interaction means phishing or social engineering campaigns could be leveraged to trick employees into triggering malicious requests. The lack of confidentiality and availability impact reduces the risk of data leakage or service disruption, but the integrity compromise alone is significant in financial contexts. Organizations in regulated sectors such as banking, insurance, and public administration in Europe may face increased scrutiny if such vulnerabilities lead to financial misstatements or fraud. Additionally, the absence of known exploits currently provides a window for proactive mitigation before active attacks emerge.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Jun 2025, 14:04 UTC

Technical details

References

Community reviews

Related threats