CVE-2025-1873
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSQL injection vulnerability have been found in 101news affecting version 1.0 through the "pagetitle" and "pagedescription" parameters in admin/contactus.php.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in 101news version 1.0 admin/contactus.php allows unauthenticated attackers to inject arbitrary SQL commands via the pagetitle and pagedescription parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm 101news software is installedSearch the web root for files containing '101news', 'news portal', or check for the presence of the /admin/ directory. Look for PHP files referencing the product name.Affected if The software '101news' or 'Mayurik Best Online News Portal' is found on the system.
-
Identify the installed versionCheck version.php, README.txt, or any version file in the application root for a version number. Also check meta tags or comments in index.php for version strings.Affected if The version is exactly 1.0.
-
Locate the vulnerable fileCheck if admin/contactus.php exists in the web document root. This is the file containing the SQL injection vulnerability.Affected if The file admin/contactus.php exists and is accessible via the web server.
-
Verify the vulnerable parameters are exposedAccess the contactus.php page via HTTP/HTTPS and inspect whether the 'pagetitle' and 'pagedescription' parameters are accepted as GET or POST input. Check if the admin panel is accessible without authentication.Affected if The pagetitle and pagedescription parameters can be submitted to the script without authentication.
-
Test for SQL injection susceptibility (optional, requires permission)Submit a single quote (') in the pagetitle or pagedescription parameter and observe if a SQL error is returned in the response. Example: admin/contactus.php?pagetitle='Affected if The application returns a SQL syntax error or unexpected database behavior in response to the quote character.
A system is affected if it runs Mayurik Best Online News Portal version 1.0 with the admin/contactus.php file accessible and the vulnerable parameters exposed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation on the pagetitle and pagedescription parameters in admin/contactus.php.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1873 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1873 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data