CVE-2018-7216
Description
Cross-site request forgery (CSRF) vulnerability in esop/toolkit/profile/regData.do in Bravo Tejari Procurement Portal allows remote authenticated users to hijack the authentication of application users for requests that modify their personal data by leveraging lack of anti-CSRF tokens.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
CSRF vulnerability in Bravo Tejari Procurement Portal allows authenticated users to modify other users' personal data via lack of anti-CSRF tokens.
Vulnerability
A cross-site request forgery (CSRF) vulnerability exists in the Bravo Tejari Procurement Portal, specifically in the esop/toolkit/profile/regData.do endpoint [1]. The application fails to include anti-CSRF tokens in its forms, allowing an attacker to forge requests that modify user profile data. The affected component is the Web Interface Management, and all versions of the Bravo Solution without CSRF protection are vulnerable [1].
Exploitation
An attacker crafts a malicious HTML page containing a forged HTTP POST request to regData.do with parameters such as userAct=confirmData and fields for name, address, and email [1]. The attacker then uses social engineering (e.g., sending a link) to trick an authenticated user into clicking the malicious form. Upon submission, the victim's browser automatically includes their session cookies, executing the unauthorized request [1]. No special network position or additional privileges beyond the victim's session are required.
Impact
Successful exploitation allows the attacker to modify the victim's personal data, including name, company address, and email address [1]. This can lead to account takeover, unauthorized access, or further phishing attacks. The attacker gains the ability to alter sensitive user information without the victim's knowledge, potentially affecting the integrity and availability of user accounts [1].
Mitigation
As of the publication date (2018-02-18), no fix has been disclosed in the available reference [1]. The vendor (Tejari) should implement anti-CSRF tokens (e.g., random tokens validated on each state-changing request) and enforce same-origin checks. Until a patch is available, users can mitigate risk by enforcing strict cookie policies, using browser extensions that block CSRF, and educating users to avoid clicking untrusted links while authenticated.
AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
Root cause
"Missing anti-CSRF tokens on the profile data modification endpoint allows forged requests to modify user personal data."
Attack vector
An authenticated attacker crafts a malicious HTML form that POSTs to `https://XXXX.XXXX.com/esop/toolkit/profile/regData.do` with parameters such as `userAct=confirmData`, `companyName`, and other profile fields [ref_id=1]. The attacker then uses social engineering to trick a victim who is already authenticated into submitting the form. Because the application does not include any anti-CSRF tokens, the victim's browser executes the forged request and the victim's personal data (name, address, email, etc.) is silently modified without their knowledge [ref_id=1].
Affected code
The vulnerable endpoint is `/esop/toolkit/profile/regData.do` in the Bravo Tejari Procurement Portal [ref_id=1]. The affected component is the Web Interface Management, specifically the profile registration data handler [ref_id=1].
What the fix does
The advisory does not include a patch or vendor fix. The recommended remediation is to implement anti-CSRF tokens (random, per-session or per-request tokens) on all state-changing forms, so that forged requests cannot be distinguished from legitimate ones [ref_id=1]. Without such tokens, any authenticated user can be tricked into modifying their own profile data via a crafted link.
Preconditions
- authThe victim must be authenticated to the Bravo Tejari Procurement Portal at the time the forged request is submitted.
- networkThe attacker must have network access to deliver a crafted HTML page or link to the victim (e.g., via email or social engineering).
- configThe application must lack anti-CSRF tokens on the /esop/toolkit/profile/regData.do endpoint.
Reproduction
1. Create an HTML file containing a form that POSTs to `https://
Generated on May 25, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
4- www.exploit-db.com/exploits/44256/mitreexploitx_refsource_EXPLOIT-DB
- seclists.org/fulldisclosure/2018/Feb/44mitrex_refsource_MISC
- packetstormsecurity.com/files/146409/Tejari-Cross-Site-Request-Forgery.htmlmitrex_refsource_MISC
- www.securityfocus.com/archive/1/541782/30/0/threadedmitrex_refsource_MISC
News mentions
0No linked articles in our index yet.