What it is
CVE-2025-2505 is an unauthenticated vulnerability affecting philsbury Age Gate. The Age Gate plugin for WordPress is vulnerable to Local PHP File Inclusion in all versions up to, and including, 3.5.3 via the 'lang'...
Vulnerability report
Age Gate
philsbury / Age Gate · * to <= 3.5.3
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2025-2505 is an unauthenticated vulnerability affecting philsbury Age Gate. The Age Gate plugin for WordPress is vulnerable to Local PHP File Inclusion in all versions up to, and including, 3.5.3 via the 'lang'...
Is it exploited?
Yes. KEV Intelligence sensors observed exploitation attempts with confirmed confidence.
Who is affected?
philsbury / Age Gate * to <= 3.5.3.
What should we do?
Patch immediately, validate internet-facing exposure, and monitor for matching requests.
Overview
The Age Gate plugin for WordPress is vulnerable to Local PHP File Inclusion in all versions up to, and including, 3.5.3 via the 'lang' parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary PHP files on the server, allowing the execution of code in those files.
This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
KEV Intelligence
Independent exploitation attestation added to the KEV Intelligence record.
KEV Intelligence sensor
First-party sensor telemetry confirms matching exploitation attempts.
Nuclei Templates
Public scanner or PoC coverage increases practical exploitability.
Per-source evidence links for KEV attestations are available through the KEV Intelligence Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| KEV Intelligence First | 2026-08-11 07:58 UTC |
Operational indicators for this CVE are listed under Detection.
Sensor telemetry
Aggregate observations show the scale, recency, and distribution of activity without overstating sparse data.
2
Attempts observed
1
Unique attacker IPs
1
Attacker countries
US
1
Sensors observed
Exploitation attempts over the last 7 days
Daily events observed by KEV Intelligence sensors
Updated 11 Aug 2026
First observed 08 Aug 2026 · Last observed 08 Aug 2026
Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Raw values available in Pro and Enterprise.
Nuclei template detected 03 Aug 2026.
View Nuclei template (opens in new tab)No KEV Intelligence virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →Attacker IP indicators observed · available in Pro and Enterprise.
Sensor-derived attacker IP indicators are available to Pro and Enterprise accounts under Detection and through the Pro API.
Learn about Pro API accessScanner and exploit-framework references linked to this CVE.
| Scanner | Reference | Detected |
|---|---|---|
| Nuclei | https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2025/CVE-2025-2505.yaml | 03 Aug 2026 |
Risk and context
CVSS v3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
3.9%
These PoCs are unverified and could contain malware. Use at your own risk.
nuclei · Created Unknown
Timeline
Evidence-backed exploitation signal
Indicators of compromise recorded
Public proof-of-concept code published
Scanner coverage available
Vulnerability disclosed publicly
Identifier reserved by the CNA
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2025-2505
Free JSON includes basic KEV fields{
"cve_id": "CVE-2025-2505",
"confidence": "Confirmed",
"cvss_score": 9.8,
"epss_score": 0.03945,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": true
},
"sensor_telemetry": { "attempts": 2, "sensors": 1 }
}