CVE-2025-7841 MEDIUM

CVE-2025-7841: Sertifier Certificate & Badge Maker for WordPress – Tutor LMS <= 1.19 - Cross-Site Request Forgery to Settings Update

Vendor Sertifier
Product Sertifier Certificate & Badge Maker for WordPress – Tutor LMS
Weakness CWE-352 · CSRF
Published August 23, 2025
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

The Sertifier Certificate & Badge Maker for WordPress – Tutor LMS plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.19. This is due to missing or incorrect nonce validation on the 'sertifier_settings' page. This makes it possible for unauthenticated attackers to update the plugin's api key via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Explanation of Vulnerability in Simple Terms

02Summary

The Sertifier Certificate & Badge Maker for WordPress – Tutor LMS plugin versions 1.19 and earlier are vulnerable to cross-site request forgery (CSRF). An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the site without the admin's knowledge or consent. The vulnerability requires user interaction—the admin must visit the attacker's page while logged into WordPress.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on the site by tricking a logged-in admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

An attacker can modify site settings or data by exploiting an admin's active session, potentially affecting certificates or badges.

Conditions required to exploit

05Prerequisites

A logged-in WordPress administrator must visit an attacker-controlled webpage while authenticated to the site.

Key dates

06Disclosure timeline

August 23, 2025 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE