CVE-2025-67173VulnerabilityPublished 17 Dec 2025

CVE-2025-67173: RiteCMS · n/a

Affects RiteCMSSource CVE Database V5

Not known to be exploited · CVSS 6.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.8Medium

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

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Dec 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 2026-10-26.

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
GitHubhandylulu/RiteCMS`pkg:github/handylulu/RiteCMS`Other threats	Affected =3.1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-67173, organizations should implement the following specific measures: 1) Apply any available patches or updates from RiteCMS as soon as they are released. 2) If patches are not yet available, deploy web application firewalls (WAFs) with rules to detect and block suspicious POST requests targeting page creation endpoints. 3) Implement anti-CSRF tokens in all forms related to page creation and editing to ensure requests are legitimate and originate from authenticated users. 4) Enforce strict user privilege management, limiting page creation and editing rights to only necessary personnel. 5) Conduct regular audits of newly created pages to detect unauthorized content promptly. 6) Educate privileged users about the risks of CSRF and safe browsing practices to reduce the likelihood of user interaction exploitation. 7) Monitor web server and application logs for unusual activity patterns indicative of CSRF attempts. 8) Consider deploying Content Security Policy (CSP) headers to reduce the impact of injected malicious content. These targeted actions go beyond generic advice and address the specific mechanics of this vulnerability.

Description

CVE-2025-67173 is a Cross-Site Request Forgery (CSRF) vulnerability in RiteCMS version 3.1.0 that allows attackers to create pages arbitrarily by sending crafted POST requests. The vulnerability requires the attacker to have some level of privileges (PR:H) and user interaction (UI:R), but it can lead to high impact on confidentiality, integrity, and availability. Although no known exploits are currently in the wild, the medium severity CVSS score of 6.8 reflects the significant risk posed by this flaw. European organizations using RiteCMS 3.1.0 should prioritize patching or implementing mitigations to prevent unauthorized content injection and potential further exploitation. Countries with higher adoption of RiteCMS or critical web infrastructure relying on it are at greater risk.

Impact

For European organizations, the impact of CVE-2025-67173 can be substantial, especially for those relying on RiteCMS 3.1.0 for their web presence. Successful exploitation could lead to unauthorized content creation, which might be used to spread misinformation, phishing campaigns, or malware, thereby damaging brand reputation and customer trust. Confidential information could be exposed if sensitive pages are created or manipulated. Integrity of the website content is compromised, potentially affecting business operations and compliance with data protection regulations such as GDPR. Availability may also be impacted if malicious pages disrupt normal site functionality or trigger automated defenses. Organizations in sectors like government, finance, healthcare, and media, which often have stringent security requirements and high public visibility, are particularly vulnerable. The requirement for high privileges and user interaction somewhat limits the attack surface but does not eliminate risk, especially in environments with multiple privileged users or insufficient user training.

Summary

CVE-2025-67173 is a security vulnerability classified as a Cross-Site Request Forgery (CSRF) affecting the page creation and editing functionality of RiteCMS version 3.1.0. CSRF vulnerabilities occur when an attacker tricks an authenticated user into submitting a malicious request unknowingly, exploiting the trust a web application places in the user's browser. In this case, the flaw allows an attacker to craft a POST request that, when executed by a user with sufficient privileges, results in the arbitrary creation of pages within the CMS. This can lead to unauthorized content injection, defacement, or the introduction of malicious content such as phishing pages or malware distribution points. The CVSS v3.1 score of 6.8 indicates a medium severity with the vector AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H, meaning the attack can be launched remotely over the network with low complexity, but requires the attacker to have high privileges and user interaction. The vulnerability impacts confidentiality, integrity, and availability, as unauthorized page creation can expose sensitive data, alter site content, and disrupt normal operations. No patches or known exploits are currently documented, but the vulnerability is publicly disclosed and should be addressed promptly. The CWE-352 classification confirms the nature of the CSRF issue. Given the nature of CMS platforms as public-facing web applications, exploitation could have significant reputational and operational consequences.

CWE-352Cross-Site Request Forgery (CSRF) (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Dec 2025, 19:32 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats