NVD / CVE Program· CNA WPScan

CVE-2021-25082: Popup Builder < 4.0.7 - LFI to RCE

HighCVSS 8.8 · v3.1—Proof of concept No fix recorded

Noroxi assessment

Priority: Monitor (action score 37/100)

A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
Public proof-of-concept code exists (Exploit-DB / GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 5.2% (FIRST EPSS); higher than 92.6% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
No fixed version is recorded, but the references include a patch (commit or PR) link.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. See the fix and affected versions sections below.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The Popup Builder WordPress plugin before 4.0.7 does not validate and sanitise the sgpb_type parameter before using it in a require statement, leading to a Local File Inclusion issue. Furthermore, since the beginning of the string can be controlled, the issue can lead to RCE vulnerability via wrappers such as PHAR

Published: Feb 21, 2022
Updated: Jun 16, 2026
EPSS: 5.2% · 92th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 2 / 30 · 5.2%

Is Popup Builder – Create highly converting, mobile friendly marketing popups. on your site?

WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
sygnoos	popup builder	cpe:2.3:a:sygnoos:popup_builder

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.

Unknown Popup Builder – Create highly converting, mobile friendly marketing popups.
- 4.0.7 and later · before 4.0.7affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

sygnoos popup builderbefore 4.0.7

Same product

sygnoos: all records

Other highest-scoring records for the same primary product.

CVE-2022-0479Popup Builder < 4.1.1 - SQL Injection to Reflected Cross-Site Scripting
52Plan
CVE-2020-9006The Popup Builder plugin 2.2.8 through 2.6.7.6 for WordPress is vulnerable to SQL injection (in the sgImportPopups function in…
42Plan
CVE-2019-14695A SQL injection vulnerability exists in the Sygnoos Popup Builder plugin before 3.45 for WordPress.
40Plan

Published before and after this one in the same product

← EarlierCVE-2020-10196Mar 13, 2020 · An XSS vulnerability in the popup-builder plugin before 3.64.1 for WordPress allows remote attackers to inject arbitrary JavaScript into…
24Monitor
← EarlierCVE-2021-24152Apr 5, 2021 · Popup Builder < 3.74 - Authenticated Reflected Cross-Site Scripting (XSS)
24Monitor
Later →CVE-2022-0228Feb 21, 2022 · Popup Builder < 4.0.7 - Admin+ SQL Injection
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Nuclei detection template ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Nuclei detection template	Nuclei template CVE-2021-25082	—

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

plugins.trac.wordpress.orgchangeset 2659117

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

JrXnm

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-22-0165 · Feb 22, 2022(WordPress Eklenti Zafiyeti)

All national notices →

Not on record for this CVE: EPSS history · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log (0)

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

plugins.trac.wordpress.org/changeset/2659117

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records